GNOME Bugzilla – Bug 340705
arrowheads on arcs leave trail when moving
Last modified: 2008-12-09 20:57:14 UTC
1. When adding arrows to arcs, the direction of the arrowhead is incorrect. 2. When dragging the arc with the arrowhead, it leaves a trail of black pixels on the screen. 3. When attempting to resize the arc, the program hung Related to bug 53060
Could you attach/link to a screenshot of issue?
Sorry cant reproduce anything beside 2) - a known issue mentioned elsewhere. For 1) I was thinking about being related to bug 331372. If you (or anyone reading this) can reproduce the issue it may be possible to get some info from the "console dump" running "dia > dia-bug.log"
For 1), do you mean that the angle of the arrow is off compared to the end of the line?
Exactly, The angle of the arrow is off compared to the end of the line. Originally I thought it was pointing the wrong way. As for 2, The trail of black pixels when dragging an arc with the arrow is still an issue that may be related.
I don't know if the arrowhead direction is still a problem, but I can reproduce the "trail of black pixels" when moving the end of the arc using today's SVN head on Linux. For the angle that is off: could you attach some sample screenshots to illustrate the problem?
*** Bug 393299 has been marked as a duplicate of this bug. ***
there are issues left with degenerated arcs but otherwise this is handled: 2007-10-06 Hans Breuer <hans@breuer.org> * lib/arrows.c : major restructuring - getting calculate and draw by function pointer. A lot of arrows are converted to the new style thus arrow_bbox() can give the correct bounding box. * objects/standard/arc.c : bug #340705 and bug #477569 objects/standard/bezier.c : bug #300055 objects/standard/line.c objects/standard/polyline.c objects/standard/zigzagline.c : not using *BBExtra to adjust the bounding box for arrows but instead a combination of arrow_bbox() and calculate_arrow_point() * lib/bounding_box.c : just a comment for now * samples/arrows.dia : more coverage
*** Bug 348611 has been marked as a duplicate of this bug. ***
*** Bug 559231 has been marked as a duplicate of this bug. ***
In version 0.96.1 it is still not resolved.
Yes, I know. Please look at the filed "Target Milestone".