Maximilian Albert wrote:
- dragging the anchor moves the whole guide (and the anchor with it)
- pressing Shift and dragging the anchor moves it along the guide
(while the guide itself stays in place) 3) dragging the guide anywhere outside the anchor rotates it around the anchor 4) pressing Shift and dragging the guide outside the anchor bypasses rotation and moves the whole guide (as in 1.)
Reading this feels like handling guides would be changed quite a bit, it doesn't feel intuitive. Maybe you should keep the existing behavior as much as possible. - drag guide (outside the anchor) - moves the guide. It's an old feature and it would be worth to consider using the same behavior as before. I often use snapping guides to objects when moving them, and Snap to nodes with Snap to closest point to cursor. I haven't thoroughly tested all the new snapping features (those I have rock!) and I don't know how your new guide features will work but maybe they will get tangled up and you should consider how they interact. - drag anchor - moves the guide but also moves the anchor along the guide. This flashed in my mind when moving the guide with snap to nodes enabled, if a person wants to snap a guide to a particular node, maybe they would want the rotation center to be there so they get it in one step. - Ctrl + drag anchor - move anchor along the guide, but the guide doesn't move (Ctrl modifier seems consistent with restricting the direction of movement) - Shift + drag guide - rotate around anchor (even if you drag at anchor)
I went for the assumption moving guides happens more often that rotating, which of course doesn't have to be true at all once this feature is implemented. Deciding about this is more complicated than it looks at first.