GNOME Bugzilla – Bug 150354
remember visibility states when Shift clicking in the layers dialog
Last modified: 2018-05-24 11:10:56 UTC
[If interested, follow up from http://bugzilla.gnome.org/show_bug.cgi? id=139874 ] Steps to reproduce the uncomfortable feeling: --------------------------------------------- 1)create 10 layers with some drawing on each. 2)change the visibility of 4 or 5 (exluding layer 1) 'At this point, you want to look at, and edit only layer1, say 3)now Shift+Click on layer1's "eye"(in layers dialog). 4)make some changes on layer 1 5)now Shift+Click on layer1's eye. OH! what a pity All other layers are visible now. ======================== <OFFTOPIC> For those wondering why people keep invisible layers, the reasons are - experimenting, backup of some other laer, etc. </OFFTOPIC> What was Expected: ------------------ When Shift+Clicking again, It should only restore the visibility of those layers that were previously visible. ===================== Solution: --------- Remember the state of the visibility of other layers when (Shift+Clicking), and restore them when the user Shift+clicks again. ===================== MAYBE Problems in the solution: ------------------------------- 1) Redefining Shift-Click Behaviour might be problematic to several people who are used to it's problem. 2)And may be also it will break previously written scripts? do they depend? 3)What must be done if the user Shift+Clicks once, preserving the state, and then continues to change the visibility of other layer? ============================== So, the Xtended Solution: ------------------------- For problems 1 and 2, 1)bind the new feature to Ctrl+Click. 2)Or as Joao S. O. Bueno said in http://bugzilla.gnome.org/show_bug.cgi? id=139874#c5, A quickmask like button would be nice making it the feature only of the interface and should not reflect the actual image. What I mean is, just make the current layer the only visible one, but only temorarily. The layers dialog will still have the "eyes" for other layers. For problem 3, Think it like doing something and then undoing it - If anything else is tampered by the user, forget the states. Follow the logic of undo and redo. that will be easier for the user to learn the "nack" of the feature. ====================[Finished(whew!)]===================================
Sorry, At the end, in the <QUOTE> For problem 3, Think it like doing something and then undoing it - If anything else ........... </QUOTE> I goofed up at "doing something and then undoing it." It should have been: "undoing something and redoing it" Also, Xtended Solution 3 is irrelavent if enhancment request http://bugzilla.gnome.org/show_bug.cgi?id=139874 is solved or Xtended Solution(2) is adopted. Thanx in advance.
Just a hint: in order to refer to another bug in Bugzilla, it is sufficient to write "bug #number", for example bug #139874. Another hint: Less is more. If you had taken the time to specofy the problem in a few lines instead of quoting lots of redundant stuff, the bug report would have been a lot more useful.
thx ;)
I don't see a point in implementing such unneccessarily complex stuff. You can simply undo the shift-clicking by hitting ctrl-z. Vote for closing as WONTFIX.
The problem is that you can't do that without undoing any action you took in the meantime. So the sequence "(1) isolate a layer, (2) do something to the layer, (3) go back to the visibility state before (1)" is not possible.
Thanx weskaggs for clarifying MY doubt ;). Or as stated in some other bugreport, it could be a button like the quickmask that "SHOWS" only the current layer. It should not modify the original image
Figure me for digging up this old bug, but I just thought I'd add: I think the only sensible way to go about this would be to have some way to put a layer into a special single-focus state. What I mean is: if you try to force GIMP to remember former visibility settings, and some how go back to them after who-knows-how much work has been done, the whole thing becomes very complex for the programmer, and less intuitive for the beginning user. Perhaps instead you could have some kind of special click on the layer (Ctrl-Alt maybe?) that highlights the layer entry with some special color, and makes only that layer visible and editable, without actually affecting the real visibility settings of all the other layers. And as soon as the user tried to do something that affects another layer (like clicking on a different layer icon, or trying to create a new layer) then the special focus of the layer disappears and all the regular visibility settings are resumed. Anyone think this concept has merit?
"special single-focus state" and "special click" does not sound like attractive UI solutions to me to be honest. Note that in GIMP 2.10 we will need to redesign the Layers dockable anyway to integrate layer groups. I'm putting this on the 2.10 milestone so we don't forget to take this problem into account when we do that.
Low priority compared to things on our roadmap, removing
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/92.