I’ve been using Krita for about a year and it’s my go-to drawing and painting program. I’ve familiarized myself with the Krita Manual on how to raise feature requests.
One thing that appears from time to time is when I have to access a layer with the R tool (
Selection mode: replace -- R) and I cannot, because it’s locked.
My typical workflow looks like this:
Paint with multiple layers packed into multiple group layers
Lock groups that no longer require edits
Notice, that there’s some crud left by accident:
Try using the
Rkey to identify the culprit
Unlock all locked groups
Ragain, this time jumping to the correct layer
Lock all group layers again
- Paint with multiple layers packed into multiple group layers
- Lock groups that no longer require edits
- Notice, that there’s some crud left by accident
Rto jump to the correct layer
- Unlock the group hosting that one layer
- Erase crud
- Lock the group hosting that one layer
- Continue work
While this isn’t something that happens often to me, maybe it’s more common for others. Also: other users may have other use cases where this situation appears. The current situation breaks the flow of work, because the more locked groups I have, the longer it takes to hunt down the crud.
IMHO this adjustments would be only a change in an existing behavior and should not require coding a separate feature. The
R key should only point to the layer without unlocking it. The decision whether to unlock should be made by the user. I see no harm in simply expanding the tree and pointing to the layer that contains the object.
Tested on Krita 4.2.8 Appimage on Ubuntu 18.04 LTS.