Hello,
There is a bug in the layers code when loading an SVG document with a single group (g element) and adding layers to it.
In this case, Inkscape will sometimes show "Root" as a layer and when I move objects between the layers, they get sometimes lost.
I even had the effect that I moved six elements and afterwards, three were in the layer and three were gone.
A couple of undos usually get the objects back.
I'd propose that you create a new artificial layer when a document has none and the user adds one (ie. after adding the first layer, the user will have two layers).
Alternatively, move all objects into the first created layer.
Or, even better, realize layers with classes. Since an object can be in several classes (you have to separate the class names with blanks, I think), objects could be in several layers at once.
Regards,
Quoting Aaron Digulla <digulla@...310...>:
There is a bug in the layers code when loading an SVG document with a single group (g element) and adding layers to it.
In this case, Inkscape will sometimes show "Root" as a layer
This is by design. "Root" shows up as a layer when it has objects in it.
and when I move objects between the layers, they get sometimes lost.
I even had the effect that I moved six elements and afterwards, three were in the layer and three were gone.
Hmm, can you give an example of how to reproduce that step-by-step?
Alternatively, move all objects into the first created layer.
That's a good idea.
Or, even better, realize layers with classes. Since an object can be in several classes (you have to separate the class names with blanks, I think), objects could be in several layers at once.
They wouldn't behave like "layers" (in the "graphic design application" sense of the word) then... not that that functionality wouldn't be nice to have under another name.
-mental
mental@...32... wrote:
There is a bug in the layers code when loading an SVG document with a single group (g element) and adding layers to it.
In this case, Inkscape will sometimes show "Root" as a layer
This is by design. "Root" shows up as a layer when it has objects in it.
Not always :-/
Take the attached file.
- Open the file - The current layer will be Root - Add a layer a - Open the layers combo. No Root layer anymore despite the fact that there are objects!! - Select the rectangles. Root's back - Select layer a. - Root's gone. - Ungroup the rectangles - Select one of them - Shift-PgDown (move it into layer a) - Hide layer a - Select a different rectangle to get root back - Add layer b - Move an object into this layer. This works ok - Hide layer b - Select another rectangle - Shift-PgDown (move it into layer b) - Shift-PgUp -> Selected layer is root but object is gone. It's still selected but invisible. You can move the handles but when you click anywhere, it's lost.
Status line shows "There is no group above this one".
mental@...32... wrote:
There is a bug in the layers code when loading an SVG document with a single group (g element) and adding layers to it.
In this case, Inkscape will sometimes show "Root" as a layer
This is by design. "Root" shows up as a layer when it has objects in it.
Oh, and can you please add a menu "move selection into layer" with the first ten layers as a submenu.
Regards,
mental@...32... wrote:
Quoting Aaron Digulla <digulla@...310...>:
In this case, Inkscape will sometimes show "Root" as a layer
This is by design. "Root" shows up as a layer when it has objects in it.
Last I checked "root" shows up as a layer when an object in it is selected. But I believe that what you have described above makes more sense.
Aaron Spike
participants (3)
-
unknown＠example.com -
Aaron Digulla -
Aaron Spike