Lock tool for toolbar request

[Brad Brighton]

I have occasion (as I'm sure almost all of us do) to show off work or otherwise review the contents of Affinity documents (Photo specifically in my case though I could also see it in each of the others) with non-users of the app interactively. It would be awesome, in my opinion, if there was a "lock toggle" that would disable any changes other than pan/zoom when enabled.

My specific use case is to put others in front of the keyboard to inspect the results without having to worry about undoing whatever they accidentally do in the process of fumbling through the project.

[Move Along People]

-

[Brad Brighton]

@haakoo That's a good workaround in the meantime, yes. Thank you.

 

EDIT: One thing about that is that it does add non-productive noise to the history; what I'm envisioning would not (though technically, depending on how various things are implemented, that may not be avoidable).

[walt.farrell]

If they know enough to make changes they probably know enough to unlock the file, too

i would be tempted to save a copy, and open that to let them look. 

[Brad Brighton]

8 minutes ago, walt.farrell said:

If they know enough to make changes they probably know enough to unlock the file, too

i would be tempted to save a copy, and open that to let them look. 

You must not have seen people fumble with trackpads before... :-D 

Exporting, saving a copy, etc are all possible but are PITAs compared to "lock/unlock edit state" so that inspection is the only thing that can be done. I can just make a mental note about the history position too and undo until I get there or "revert to saved" (which should also be a one-step feature but isn't) but that doesn't (to my way of thinking) negate the usefulness of the feature request.

EDIT: To be clear, I'm not talking about security from intentional changes; this is about blocking accidental/incidental changes caused by clicking, dragging, and otherwise fumbling through pan/zoom.

Edited July 10, 2019 by Brad Brighton
Add the clarification about what this request is actually protecting from

[Old Bruce]

9 minutes ago, Brad Brighton said:

To be clear, I'm not talking about security from intentional changes; this is about blocking accidental/incidental changes caused by clicking, dragging, and otherwise fumbling through pan/zoom.

Your best bet is to save a copy and let them see that. Or take a snapshot, restore the snapshot immediately so you have a history entry to return to. Name it (the snapshot) Pause for review 01.