mental@...3... wrote:
Quoting bulia byak <buliabyak@...400...>:
I remember you were talking about it showing even down to individual objects if you expand the tree.
I'm leaning away from that now after our last conversation on the topic (some time ago). Among other things, selection of layers (sets the current layer) is very different to selection of objects (selects objects).
I'll start off with, I don't have a particularly strong preference as to which way it works, but the way Bulia mentioned seems more appealing to me.
My question is, how does what you describe above conflict? Is it because technically one is setting and the other is selecting? I think that the dialog would basically be context sensitive. If you're selecting (setting) a layer it behaves as you'd expect. If you need to select (really select) all objects on a layer that's already handled by the Select All function (since it does by current layer). And if you are selecting a child object of that layer, it works as you'd expect there... selecting it. I think that handling down to individual objects in the layer dialog then gives the benefit of easily hiding/unhiding and locking/unlocking objects (which those are not easy for new users to figure out how to achieve... specifically getting objects unhidden or unlocked).
I will say though that what you propose in terms of "classic" layer dialog and enhanced xml editor is quite appealing as well. I'll just be happy to have an easier way to work with layers (specifically the hiding & locking functions). Should I get excited, or is it too soon? :)
-Josh