problems when opening file from 0.47 in 0.48
Hi all,
I'm testing the 0.48 version and I've noticed that when opening an svg file created in version 0.47 in 0.48, some elements (arrows, in this specific case) that I had grouped with a main figure with other elements (rectangles, circles, etc..), now the arrows appears far away from the main figure in the canvas. Is that any known issue or problem ?
Best regards,
Rafael Z. Frantz PhD Student University of Sevilla - Spain http://www.tdg-seville.info/rzfrantz
*Guaraná *for Enterprise Application Integration http://www.tdg-seville.info/rzfrantz/guarana
Seeking for a paper? Try TDG Scholar at http://scholar.tdg-seville.info
On 19/8/10 14:34, Rafael Z. Frantz wrote:
I'm testing the 0.48 version and I've noticed that when opening an svg file created in version 0.47 in 0.48, some elements (arrows, in this specific case) that I had grouped with a main figure with other elements (rectangles, circles, etc..), now the arrows appears far away from the main figure in the canvas. Is that any known issue or problem ?
By arrows - you mean connector lines (with arrow markers)?
possibly related:
Bug #556467 “connectors between groups misplaced (regression)”: https://bugs.launchpad.net/inkscape/+bug/556467
or, a regression as described here (not filed separately): https://bugs.launchpad.net/inkscape/+bug/552289/comments/4
but difficult to tell without actual access to the SVG file: please report a bug and attach the file in question for further investigation.
~suv
Rafael,
I'm testing the 0.48 version and I've noticed that when opening an svg file
created in version 0.47 in 0.48, some elements (arrows, in this specific case) that I had grouped with a main figure with other elements (rectangles, circles, etc..), now the arrows appears far away from the main figure in the canvas. Is that any known issue or problem ?
I suspect that this is due to nested <svg> elements; there were some fairly serious issue in 0.47 with those, where the positions would get messed up and go weird and occasional crashes would result. It happened that in some way the internal representation was incorrect (relative positions in the child <svg> elements) but Inkscape didn't quite realise that and rendered the positions correctly (mostly). This may have been fixed for 0.48, so that may be the reason why - it's rendering them *properly* now, and so it doesn't appear the same as in 0.47. If you can provide the actual files you're experiencing it with the issue could be analysed more accurately - it may be that there is a bug in 0.48 and it would be helpful to verify it.
Regards,
Chris Morgan
Dear Chris and ~suv,
I've opened this bug report and uploaded the svg file. Hope this help to check whether it is a potential bug or not.
https://bugs.launchpad.net/inkscape/+bug/620486
Thank you very much!
Best regards,
Rafael Z. Frantz PhD Student University of Sevilla - Spain http://www.tdg-seville.info/rzfrantz
*Guaraná *for Enterprise Application Integration http://www.tdg-seville.info/rzfrantz/guarana
Seeking for a paper? Try TDG Scholar at http://scholar.tdg-seville.info
On Thu, Aug 19, 2010 at 3:07 PM, Chris Morgan <chris.morganiser@...400...>wrote:
Rafael,
I'm testing the 0.48 version and I've noticed that when opening an svg file
created in version 0.47 in 0.48, some elements (arrows, in this specific case) that I had grouped with a main figure with other elements (rectangles, circles, etc..), now the arrows appears far away from the main figure in the canvas. Is that any known issue or problem ?
I suspect that this is due to nested <svg> elements; there were some fairly serious issue in 0.47 with those, where the positions would get messed up and go weird and occasional crashes would result. It happened that in some way the internal representation was incorrect (relative positions in the child <svg> elements) but Inkscape didn't quite realise that and rendered the positions correctly (mostly). This may have been fixed for 0.48, so that may be the reason why - it's rendering them *properly* now, and so it doesn't appear the same as in 0.47. If you can provide the actual files you're experiencing it with the issue could be analysed more accurately - it may be that there is a bug in 0.48 and it would be helpful to verify it.
Regards,
Chris Morgan
participants (3)
-
Chris Morgan -
Rafael Z. Frantz -
~suv