Moving nodes with Shift key is broken.
-
https://recordit.co/9pGjeNdnbF
Moving nodes along the lines using the shift key does not work as expected. The problem mainly affects single nodes, I can't remember if I had a problem when I moved several nodes at the same time.
-
@encart What are you feeling it needs to do differently? I saw your video and also experimented myself and it seemed fine to me.
If you move the node too far from the original straight vertical or horizontal path - it will eventually create a new angle, but that seems normal behavior to me.
-
@encart I think I managed to replicate the issue. It seems that in case of lines, two features (constraining angle and constraining direction) collide. I have to find a better modifier assignment for these.
-
@encart @Boldline @vectoradmin If 'Angle Constraint' in Prefs > Editing Options is not the default 45°, Shift-moving a node will be constrained diagonally at multiples of the custom angle (15, 30, 45, 60, 75, 90 if custom angle is 15°). This also causes unexpected jumping.
Maybe Shift-moving nodes should stick to horizontal, vertical and 45° angle, no matter the 'Angle Constraint' in Preferences?
Or to horizontal, vertical and the angle of the node's segment?
-
I thought about this and in my opinion Shift-moving (sliding) a node along the angle of its segments would be the most useful option. Shift-moving it at 45° or whatever custom angle you have in Prefs seems almost arbitrary most of the time — rarely useful.
Agree? Disagree?
Anyway… A nice thing to have with Shift-moving nodes would be a very thin dashed line that indicates the direction/angle along which the node is moved.
-
@b77 Currently the conflict (between two active features is):
- moving the node horizontally or vertically from the starting location.
- keeping the angle the line before the node at some constrained angle (multiple of 45 degree in this case).
The error is that both of these are done in some cases.
I agree that (1) is not that interesting, how about (2)?
-
@vectoradmin So having all three (0°, 90° AND 45°) is the conflict?
Constraining at 0°, 90° AND 45° is better than just at 0° and 90°, but in my opinion the 45° is not that useful in "real life".
I suggested that instead of the 45° constrain to have the app constrain the node moving to whatever angle the adjacent segments are… 27°, 51°, etc.
And if any of the segments are perfectly horizontal or vertical, let the 45° constrain kick in.
Or have a different keyboard modifier assigned for this?
Sorry if I misunderstood something.
-
@b77 I will try to find a good solution for this one.
-
@encart Moving nodes with Shift+ key held should constrain the movement direction now.
