Too easy to lock/hide a group object after entering it

[Bug Importer]

The two ui actions Layer Visibility and Layer Lock do
also operate on individual objects and paths and
presumably also on individual nodes in paths.

This leads to problems when entering a group and then
locking some object within that group, with the user
still thinking that layer locking or layer visibility
will only lock the layer or make the layer visible or
hide it respectively.

This even leads to a state where the group that
contains the locked object can no longer be edited. You
will have to modify the XML source directly in order to
make the group accessible again.

[Buliabyak-users (buliabyak-users)]

Here's how I understand this request: We discourage
locking/hiding individual objects because there's no easy
way to unlock/unhide them, and encourage locking/hiding
layers instead. However, by entering a group and
hiding/locking it as layer, we do exactly this discouraged
thing: now if we leave the group we can't enter it again and
can't easily unlock/unhide it.

[Buliabyak-users (buliabyak-users)]

Originator: NO

now we have unlock all/unhide all commands for such emergency situations