Layer Locking Needs To Actually Lock

[VectorVonDoom]

It happens from time to time where I accidentally delete a group (sometimes the whole thing but that's easy to spot!), it can be from pressing delete once too many times to delete a path but the reason doesn't really matter, it happens. So far I've either noticed and done undo's (which can still mean you've lost things) or copied it back from a backup. It happened just now, I was just about to quit noticed I'd managed to delete a group, which was fortunate as it is new so no backup. It's the sort of thing that if I did loose a big chunk of work because of it I'd be very tempted to bin it.

So locking needs to actually lock, nothing can be done to it at all unless you unlock. Basically like any other app I can think of. I don't care if that's the new default behavior or it's an option.

[Pšenda]

10 hours ago, VectorVonDoom said:

So locking needs to actually lock, nothing can be done to it at all unless you unlock. Basically like any other app I can think of. I don't care if that's the new default behavior or it's an option.

Unfortunately, Serif does not see/understand the importance of truly locking the contents of a layer.

 

 

[VectorVonDoom]

Another way I noticed that I accidentally delete stuff (possibly the main way) is managing to bring up the layers context menu when toggling visibility of layers (checkbox) using the trackpad by touching with 2 fingers by accident (with macbook touch to click option enabled it does happen, very sensitive). It's not normally a big deal in apps however Cut is the first option and can end up being selected.