Follow-up Comment #3, bug #20359 (project mypaint):
> Thank you for reporting it so concisely and thoroughly! Post-1.1, I think:
it's quite a lot of work, just internally since the code currently makes a lot
of assumptions about stack layout.
No problem! The way I see it, if I can't take the time to explain what I want
well, I can't expect someone else to take the time to do it. I would have
requested it long ago, but for some reason I assumed ORA couldn't do it
without a change to spec. Only recently saw otherwise I saved to the format
in Krita.
> Layer move - what happens if you move the bottom layer of a tree?
Presumably the whole stack will have to move with it. Not fun with a tiled
memory structure, but at least we have much of the work done.
If you mean moving a layer within canvas, only the layer you move would be
affected. To adjust all layers you adjust the group itself, which gets
displayed as an adjustable layer. At least, that's how Krita does it, and
gimp seems to act similarly, though I only tested it briefly.
For example, if you have a document with the following group structure: group
"Foo" with four layers ("sketch" "inks" "flats" "shading"), a background, and
a foreground, the layout would be something like this (assuming formatting
works in my favour):
* Foreground
* Foo
* * Inks
* * Shading
* * Flats
* * Sketch
* Background
You could select 'Foo', which is a group layer, and set things like its
opacity and visible-ness. If you select 'Foo' and move the layer, then the
four child layers will be moved at the same time, all in sync with each other.
If, instead, you select "Sketch" and move it, it will move independently of
the other layers.
It would be silly in the example I gave, but less so if you had, say, a group
called "Dialogue Boxes" for a comic: you could move or change visibility of
all boxes at once, but still rearrange them within the comic manually by
adjusting the individual layers.
That's assuming I understood the question correctly, of course.
> Dragging in the layers list, adding new layers (inside current, top
level), merging...
To continue using Krita as an example, since I'm more familiar with its
implementation than Gimp's: Krita always tries to add a new layer within the
active group, directly above the currently selected layer. If the selected
layer is a group layer, then it adds the new layer to the top of the group's
stack.
Dragging generally figures out the appropriate context, though it's not
perfect, at least with regard to placing a layer between the end of one group
and the beginning of the next. UI buttons exist for moving into and out of
groups, though, represented as left and right arrows (← and →).
I just tested the group merging behaviour, and it looks like Krita flattens
the group for all group-related merges. Merge a single layer onto a group,
and it flattens the group and then makes a single layer from merging that
composite with the other layer. Likewise for group-on-group: both are
flattened then merged. This surprised me, actually: it's *extremely*
destructive behaviour that is also fairly obtuse.
Gimp won't allow you to merge layer groups into other layers at all. Layers
inside a group can be merged together, layers outside can, but never shall a
group itself merge.
I personally think Gimp's behaviour is the correct choice here, even if it is
less convenient. Maybe Krita-style merging with a warning box of some kind?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?20359>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
