Coordinates don't update properly when moving a node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Low
|
Matthew Petroff |
Bug Description
Inkscape 0.48.4 r9939
Windows 7 x64 SP1
Bug:
When moving a particular node by the keyboard arrows, the X,Y coordinates of the node do not update properly. This doesn't happen everywhere, but only in a few places.
Steps to reproduce:
1. Load the attached file.
2. Then go into the the 'Edit paths by node' mode, & find the node located @ X 399; Y 401 and select it. (It's the node at the top of the middle green line.)
3. Using your keyboard, hit the down arrow to move the node to X 399; Y 399
What should happen:
The coordinates for 'Y' should update to display the new location of the node @ Y 399.
What happens:
The coordinates for 'Y' don't properly update and show the node @ Y 401 still, even though it has been moved to Y 399.
This bug is also happening with the top node of the other two green lines in the attached file (X 397; Y 399) (X 401; Y 403). With both of them, if you just substitute each of their top nodes into Step 2 and then do Step 3 with them, the Y coordinates box doesn't update as well. Don't know how far this bug happens, but it seems to continue on the diagonal in both directions from the three lines.
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
On OS X 10.7.5:
- reproduced with Inkscape 0.48.4 r9939, r10025
- not reproduced with 0.48+devel r13393
Based on tests with archived builds: bazaar. launchpad. net/~inkscape. dev/inkscape/ trunk/revision/ 12471>
- reproduced with rev <= 12470,
- not reproduced with rev >= 12471;
this appears to have been fixed by the changes of the GSoC unit refactoring branch which was merged in revision 12471:
<http://