Diederik van Lierop wrote:
On 07/07/2009 12:33 AM, bulia byak wrote:
...
We should allow for free translation of the guide and constrained translation of its origin. Most logically the former should have no modifier key, whereas the latter should use the ctrl key because in many other case the ctrl-key is used for constraining already. But as you noticed the ctrl-key has already been assigned to deleting. On top of that, rotating the guide and translating the origin, which are two very different things, are both activated by shift, and the distinction between these two modes is in where you grab the guide. Once you're used to that it's OK, but it's not very straightforward. It's much cleaner to have it like this:
no modifiers for moving shift for rotation ctrl for constraining delete for deleting
So we will end up like this A) when dragging with no modifiers we will move the origin to the pointer location (freely, in 2D) B) with ctrl we will have a constrained translation of the origin along the guide
I might be too late, but it seems to me that we will have more consistent behavior if we follow existing keybinding of other tools. For example, here is what "Inkscape keyboard and mouse reference" says,
*Ctrl+Alt+mouse drag - move along handles* This restricts movement to the directions of the node's handles, their continuations and perpendiculars (total 8 snaps).
Ignoring rotation part, Ctrl+Alt will, with this modification, still move handle point along (guide) line.
This small change would make behavior of somehow similar tools (to some extent), well, similar. The only difference would be Shift becoming from - no-snap modifier to - rotate modifier.
Hope this will be considered, at least. Vlada
C) with shift we will rotate D) with ctrl-shift we will rotate to increments of the absolute angle E) when pressing delete when hovering above a guide in the selector tool, or while dragging a guide, the guide will be deleted. We can even add a context menu as Luca suggested
If I remember correctly then this quick-deleting was not available in v0.46, or was it? We'd better change (or at least find consensus on either solution) now, before we hit the masses!
Diederik