rotating guides

[SorinN]

Yep in a new compilation - I discovered what I search on the place
where - I think - any Corel Draw / Illustrator designer look first for
supplementary info's - on status bar.

Now the circle is complete -> It's easy to find that functionality.


2009/6/27 Alexandre Prokoudine <alexandre.prokoudine@...>:

> On Fri, Jun 26, 2009 at 12:07 PM, LucaDC wrote:
>
>> Personally I had some difficoulties too in understanding how to manage guides
>> when the little circle first appeared,
>
> Luckily thanks to changes by bulia this doesn't seem to be a problem anymore :)
>
> Alexandre
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@...
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>

--
Nemes Ioan Sorin

------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Diederik van Lierop]

Hi

About the guides once again :-) :

There's still something unintuitive with the guide's origin IMHO. When
you try to drag the origin and try to snap it to something, you'll find
out at some point that you didn't grab the origin but that you instead
grabbed the guide itself. And if you really grab the origin itself (with
SHIFT), you'll notice that you can only move it along the guide and not
freely over the canvas in 2D. That's really something that we miss now.
So I propose the following:
1) only when pressing shift, the origin should appear, then
2a) when grabbing the guide far away from the origin, it should rotate,
2b) when grabbing it close to the origin, we should be able to move the
origin in two dimensions (currently it only moves in 1D, i.e. along the
guide itself)
3) only when pressing both ctrl AND shift, the motion of the origin
should be constrained to the guide like it is now

Wouldn't that make more sense?

Diederik

------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[LucaDC]

These are my humble suggestions:
1) when moving the guide (no modifiers) you always also move (and snap) the origin, that goes under the cursor, in 2D (so wherever you click you always grab the guide at its origin: why moving the guide keeping the origin at the original distance from the grab/snapping point?); this behaviour would be consistent (=intuitive) to what happens when you create a guide;

2) if shift is pressed when clicking, the guides always rotate (snapping to what's around or, if you press ctrl after the rotation is started, to absolute angles, i.e. always starting from 0, using the step specified in the preferences for when rotating objects);

3) if ctrl-shift is pressed when clicking, the origin moves constrained to the guide (snapping to what's around projected perpendicularly to the guide; if you want something different you can create a new guide and snap to the intersection, while creating a guide perpendicular to a given one is not always straightforward; this is a general consideration regarding snapping while constrained).

4a) the circle should appear when hovering on the guide (so whenever it becomes selected);
  or
4b) the circle should appear when you start moving the guide in 2D (so under the cursor), or when a modifier is pressed (but you must select the guide also, to avoid having all the origins of all guides in the drawing appear whenever you press a modifier, maybe for doing something else with another tool);

Points 2) and 3) could be implemented as they are now (i.e. you get the two clicking on the guide at different distances from the origin) provided that the cursor and status bar indications change correctly to show the difference (now they don't). This would eliminate the ctrl-shift modifier. I can't decide what is better: modifiers let you select directly the operation you want to perform (which I prefer), but you must know them... :)

Luca

Diederik van Lierop wrote:

Hi

About the guides once again :-) :

There's still something unintuitive with the guide's origin IMHO. When
you try to drag the origin and try to snap it to something, you'll find
out at some point that you didn't grab the origin but that you instead
grabbed the guide itself. And if you really grab the origin itself (with
SHIFT), you'll notice that you can only move it along the guide and not
freely over the canvas in 2D. That's really something that we miss now.
So I propose the following:
1) only when pressing shift, the origin should appear, then
2a) when grabbing the guide far away from the origin, it should rotate,
2b) when grabbing it close to the origin, we should be able to move the
origin in two dimensions (currently it only moves in 1D, i.e. along the
guide itself)
3) only when pressing both ctrl AND shift, the motion of the origin
should be constrained to the guide like it is now

Wouldn't that make more sense?

Diederik

------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Diederik van Lierop]

Op Wo, 1 juli, 2009 12:01, schreef LucaDC:
> These are my humble suggestions:
> 1) when moving the guide (no modifiers) you always also move (and snap)
> the
> origin, that goes under the cursor, in 2D (so wherever you click you
> always
> grab the guide at its origin: why moving the guide keeping the origin at
> the
> original distance from the grab/snapping point?); this behaviour would be
> consistent (=intuitive) to what happens when you create a guide;

That makes sense! If no one comes up with a valid use case for the current
behavior then I will implement it the way you suggest.

> 2) if shift is pressed when clicking, the guides always rotate (snapping
> to
> what's around or, if you press ctrl after the rotation is started, to
> absolute angles, i.e. always starting from 0, using the step specified in
> the preferences for when rotating objects);

So shift rotates ...

> 3) if ctrl-shift is pressed when clicking, the origin moves constrained to
> the guide (snapping to what's around projected perpendicularly to the
> guide;
> if you want something different you can create a new guide and snap to the
> intersection, while creating a guide perpendicular to a given one is not
> always straightforward; this is a general consideration regarding snapping
> while constrained).

... but when "adding ctrl to shift" not only it becomes constrained, but
it also changes from rotation to translation. In my opinion using ctrl
should only make the motion constrained, and not change the type of
transformation simultaneously.

So:
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
C) with shift we will rotate
D) with ctrl-shift we will rotate to increments of the absolute angle

and with A), B), and C) Inkscape will snap depending on the snapping
parameters.

It looks like we're converging here, aren't we ;-) ? What do you think?

Diederik


------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[LucaDC]

Good.
I'd only warn about using ctrl alone as modifier as it's already in use to delete the guide.
You could end up in accidentally deleting the guide of which you want to move the origin.

Luca

Diederik van Lierop wrote:

So:
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
C) with shift we will rotate
D) with ctrl-shift we will rotate to increments of the absolute angle

and with A), B), and C) Inkscape will snap depending on the snapping
parameters.

It looks like we're converging here, aren't we ;-) ? What do you think?

Diederik


------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Diederik van Lierop]

On 07/06/2009 10:35 AM, LucaDC wrote:

I'd only warn about using ctrl alone as modifier as it's already in use to delete the guide.
You could end up in accidentally deleting the guide of which you want to move the origin.
  

Good point, I hadn't thought of that yet but I would have certainly run into this problem. Thanks!

1) We could distinguish between pressing ctrl before or after pressing the mouse button, but that's not very attractive.
2) We could leave the ctrl key for deleting, and do a constrained translation of the origin only when the guide is grabbed near its origin, and do a free translation of the guide when grabbing it elsewhere (and positioning the origin at the location where we release the mouse button).
3) We could find another way to easily delete guides and use ctrl for constrained translation. That's what most consistent because ctrl is used in
many cases already for constrained transformations. But I'm afraid that people already got used to ctrl-click deletion, so we will have to find a
_really_ good alternative if we want to get consensus on this.  What about pressing the delete key when already dragging? It's a bit more laborious than just ctrl-click, but it's close to being perfect IMHO. Any other suggestions?

Diederik

Diederik van Lierop wrote:
  

So:
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
C) with shift we will rotate
D) with ctrl-shift we will rotate to increments of the absolute angle

and with A), B), and C) Inkscape will snap depending on the snapping
parameters.

It looks like we're converging here, aren't we ;-) ? What do you think?

Diederik


------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel


    

------------------------------------------------------------------------------

_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[bulia byak]

On Mon, Jul 6, 2009 at 4:48 PM, Diederik van Lierop<mail@...> wrote:

> 1) We could distinguish between pressing ctrl before or after pressing the
> mouse button, but that's not very attractive.
> 2) We could leave the ctrl key for deleting, and do a constrained
> translation of the origin only when the guide is grabbed near its origin,
> and do a free translation of the guide when grabbing it elsewhere (and
> positioning the origin at the location where we release the mouse button).
> 3) We could find another way to easily delete guides and use ctrl for
> constrained translation. That's what most consistent because ctrl is used in
> many cases already for constrained transformations. But I'm afraid that
> people already got used to ctrl-click deletion, so we will have to find a
> _really_ good alternative if we want to get consensus on this.  What about
> pressing the delete key when already dragging? It's a bit more laborious
> than just ctrl-click, but it's close to being perfect IMHO. Any other
> suggestions?

What's wrong with only constrained rotating with Ctrl+Shift, and
deleting with Ctrl? This is what we have in the code right now and it
works for me.

--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org

------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[LucaDC]

The reason I didn't suggest to think about a new way to delete guides is the same that you explained: it's really difficoult to find a good alternative. Ctrl-click is strange (I often did it by mistake at the beginning) but when you get used it's easy. I was used to drag the guide outside the canvas but now I never do so anymore (also if I've seen it works in Inkscape too now, I can't say since when).

Left-click and select "delete guide"? Now there is no specific context menu for guides.
But the new command should be very quick as the plugin for deleting all guides is not easily reachable and one could need to delete a lot of guides but not all existing ones.

I really have no other suggestions but either keeping the distance-dependent-click or introducing a new modifier. Up to now I would keep the former as it's already implemented.
I agree it's a pity that ctrl-click was allocated to something that has nothing to do with constrained moving. Personally I could sacrifice the quick-deleting command to coherence, but I feel it's not a practical solution.

Luca

Diederik van Lierop wrote:

 


On 07/06/2009 10:35 AM, LucaDC wrote:

  I'd only warn about using ctrl alone as modifier as it's already in use to delete the guide.
You could end up in accidentally deleting the guide of which you want to move the origin.
 


Good point, I hadn't thought of that yet but I would have certainly run
into this problem. Thanks!

1) We could distinguish between pressing ctrl before or after pressing
the mouse button, but that's not very attractive.
2) We could leave the ctrl key for deleting, and do a constrained
translation of the origin only when the guide is grabbed near its
origin, and do a free translation of the guide when grabbing it
elsewhere (and positioning the origin at the location where we release
the mouse button).
3) We could find another way to easily delete guides and use ctrl for
constrained translation. That's what most consistent because ctrl is
used in
many cases already for constrained transformations. But I'm afraid that
people already got used to ctrl-click deletion, so we will have to find
a
_really_ good alternative if we want to get consensus on this.  What
about pressing the delete key when already dragging? It's a bit more
laborious than just ctrl-click, but it's close to being perfect IMHO.
Any other suggestions?

Diederik


 

Diederik van Lierop wrote:
 
 
    So:
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
C) with shift we will rotate
D) with ctrl-shift we will rotate to increments of the absolute angle

and with A), B), and C) Inkscape will snap depending on the snapping
parameters.

It looks like we're converging here, aren't we ;-) ? What do you think?

Diederik


------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel 


   
 
 
 






------------------------------------------------------------------------------

_______________________________________________
Inkscape-devel mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Diederik van Lierop]

On 07/07/2009 12:33 AM, bulia byak wrote:

On Mon, Jul 6, 2009 at 4:48 PM, Diederik van Lieropmail@... wrote:
  

1) We could distinguish between pressing ctrl before or after pressing the
mouse button, but that's not very attractive.
2) We could leave the ctrl key for deleting, and do a constrained
translation of the origin only when the guide is grabbed near its origin,
and do a free translation of the guide when grabbing it elsewhere (and
positioning the origin at the location where we release the mouse button).
3) We could find another way to easily delete guides and use ctrl for
constrained translation. That's what most consistent because ctrl is used in
many cases already for constrained transformations. But I'm afraid that
people already got used to ctrl-click deletion, so we will have to find a
_really_ good alternative if we want to get consensus on this.  What about
pressing the delete key when already dragging? It's a bit more laborious
than just ctrl-click, but it's close to being perfect IMHO. Any other
suggestions?
    

What's wrong with only constrained rotating with Ctrl+Shift, and
deleting with Ctrl? This is what we have in the code right now and it
works for me.
  

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
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


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Maximilian Albert-2]

2009/7/8 Diederik van Lierop <mail@...>:

> 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
> 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!

I agree. And I'd vote for the above suggestion, too, because it's the
most consistent and foreseeable. Indeed, quick-deleting with
Ctrl+click was introduced not so long ago, more or less as a quick
solution and because it wasn't foreseeable that full
translation/rotation abilities of guides were going to be implemented
soon. Now that these are availabe I'd personally vote for the more
consistent set of controls as described by Diederik above. The only
small thing is that I find it a bit inconvenient to use Delete because
it's located at the top right corner of the keyboard instead of
conveniently on the lower left. But it's still good enough, I guess.
Perhaps we can additionally have something like Ctrl+Alt+Click for
quick-deletion (or something similar; I don't know what would be most
appropriate)?

Max

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Alexandre Prokoudine]

On Tue, Jul 7, 2009 at 11:13 PM, Diederik van Lierop wrote:

> If I remember correctly then this quick-deleting was not available in v0.46,

Oh, it surely was. One of the best additions to that release :)

Alexandre

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Diederik van Lierop]

On 07/08/2009 04:44 AM, Maximilian Albert wrote:

2009/7/8 Diederik van Lierop mail@...:

  

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
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!
    

I agree. And I'd vote for the above suggestion, too, because it's the
most consistent and foreseeable. 

Hi Max, thanks for chimming in!

So if no one has any serious objections then I'll go ahead and change this as soon as possible.

Diederik

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[LucaDC]

For what it's worth, I suppose you already know that I completely agree.
I hope you'll find time to work on it soon.

Luca

Diederik van Lierop wrote:

 


On 07/08/2009 04:44 AM, Maximilian Albert wrote:

  2009/7/8 Diederik van Lierop <[e-mail]> :

 
 
    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
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!
   
 
 
I agree. And I'd vote for the above suggestion, too, because it's the
most consistent and foreseeable.


Hi Max, thanks for chimming in!

So if no one has any serious objections then I'll go ahead and change
this as soon as possible.

Diederik




------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Diederik van Lierop]

On 07/13/2009 12:07 PM, Maximilian Albert wrote:

Hi Diederik,

  

Hi Max, thanks for chimming in!

So if no one has any serious objections then I'll go ahead and change this
as soon as possible.
    

Have you started working on this yet? I have very limited time
resources right now but I feel that if I work on anything at all it
would be best to choose some part of the code base I'm familiar with
and an easy task. So I guess changing the guide behaviour would be a
good way to disburden you somewhat and give you more time to continue
your awesome bug hunt. :-) Let me know what the status is.

Best regards,
Max

  

No, I haven't started on this yet so please go ahead. Don't worry about me, I don't get bored that easily ;-).

Diederik

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Maximilian Albert-2]

2009/7/8 Diederik van Lierop <mail@...>:

> 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
> 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

I just commited the corresponding changes to SVN (rev. 21846). Please
test extensively and report anything which is not yet as desired or
can still be improved. Apart from the things listed above, I also made
the cursor switch correctly between rotation and translation depending
on whether Shift is pressed or not (this didn't work 100% before) and
also removed the info about keyboard modifiers from the guides dialog
(the one which opens when double-clicking on a guide) because it's
essentially useless there and consumes a lot of space.

Some comments or issues I couldn't resolve:

1) There is a strange bug which can reproduced as follows: Start
Inkscape afresh and drag a guide out of the ruler. Then hover the
mouse over it and press Delete. Nothing happens, and the status bar
shows the message "Nothing was deleted". Now click anywhere on the
canvas, hover again over the guide and press Delete. This time the
guide gets deleted as intended. Even when the canvas-click occurs
before creating the guide, everything is normal. It seems a bit like
the canvas first has to be "activated" before keyboard events are
processed correctly.

The reason for this strange behaviour is that the first time the key
press is not propagated to sp_dt_guide_event() but gets caught earlier
and is then processed in sp_selection_delete(). However, after the
canvas-click the propagation to sp_dt_guide_event() works fine. I have
no clue where this comes from and any hints are greatly appreciated.
BTW, this is also the reason why the cursor doesn't change when you
hover over a newly created guide and press Shift (this also only works
after a canvas-click).

2) I don't know what to include in the status bar message. With a
description of all modifiers the message is definitely too long. Right
now I have it say "Shift+drag to rotate, Ctrl+drag to move origin, Del
to delete". In particular, I dropped "Drag to move" because it seemed
to me that users would expect this intuitively. Other suggestions?

3) IMHO it would be nice if the kind of guide movement could change
interactively when pressing/releasing a modifier while dragging a
guide. For example, when we start dragging and press Shift (while
continuing to drag) it would be nice if the motion switched to a
rotation. Or when starting to move the origin by Ctrl+dragging and
releasing the Ctrl key then the motion should switch to regular
dragging. What do you think? I tried to implement this but encountered
a bug similar to the one described in (1) which prevents some keyboard
events from being passed to sp_dt_guide_event(). I'm not sure if it's
caused by the same thing, though. Any hints where to look are again
highly appreciated.

4) LucaDC said he felt that the new cursor which appeared when
dragging a guide conveyed a feeling of imprecision, so I changed it
back to the original arrow-shaped cursor. For rotation, however, I
still use the new cursor. Is everyone happy with that?

5) In principle, snapping guides to other objects should work, but I
only manage to snap guides to other guides and to nothing else.
Diederik?

6) As mentioned above, guides are now deleted by pressing Del when
hovering over them. Is this sufficient or should we implement a second
shortcut similar to the original one (like Alt+Ctrl+click)?

Thanks for any comments!
Regards,
Max

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Diederik van Lierop]

On 07/16/2009 05:31 PM, Maximilian Albert wrote:

> I just commited the corresponding changes to SVN (rev. 21846). Please
> test extensively and report anything which is not yet as desired or
> can still be improved.

Works like a charm! This behavior is far more intuitive IMHO!

One thing we could add is that ctrl-clicking on a guide at some distance
of the origin immediately moves the origin to that position on the
guide. Now you first have to get the origin and drag it to where you
want it.

> 5) In principle, snapping guides to other objects should work, but I
> only manage to snap guides to other guides and to nothing else.
> Diederik?
>  

Snapping to objects works for me. Did you select the "snap to cusp
nodes" button on the snap toolbar? By default no snap target is enabled,
only the guides and the grids. Guides do not snap to grids yet, I still
need to implement that.
> 6) As mentioned above, guides are now deleted by pressing Del when
> hovering over them. Is this sufficient or should we implement a second
> shortcut similar to the original one (like Alt+Ctrl+click)?
>  

While dragging or rotating a guide and pressing delete, nothing happens.
However when I'm dragging the origin with ctrl, pressing del deletes the
guide.

Thanks for your work Max, it's much appreciated!

Diederik



------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Tavmjong Bah]

Hi,

        Is it possible to prevent the guide line from being moved when double
clicking on it (i.e. when opening the guide-line dialog)? The movement
make the "Relative change" option rather pointless as well as messing up
carefully set x and y values.

                                                Tav



------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Vladimir Savic-3]

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

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Maximilian Albert-2]

Hi Tav,

>        Is it possible to prevent the guide line from being moved when double
> clicking on it (i.e. when opening the guide-line dialog)? The movement
> make the "Relative change" option rather pointless as well as messing up
> carefully set x and y values.

Sorry, but I cannot reproduce the problem. When I manually set the
position of a guide (e.g., via the guidelines dialog itself) and then
double click on it, I always get the same coordinates back when the
dialog opens. Can you give precise steps how to see the problem?

Best,
Max

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

[Maximilian Albert-2]

2009/7/17 Vladimir Savic <vladimir.firefly.savic@...>:

> I might be too late, [...]

It is never too late in open source software. :-) However, I'd like to
hear other people's opinions on this before implementing it because
I've used Inkscape very little for real production work lately so that
I feel I can't thoroughly judge usability questions.

> 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.

I'm not sure if I understood the last paragraph correctly. Just to
make sure, your suggestion is to use Ctrl+Alt instead of Ctrl for
moving the anchor along the guide, right? Frankly, I'm not convinced.
If we implement this change then the Ctrl modifier (whithout Alt) will
be unused. Firstly, this forces the user to unnecessarily press a
second modifier to obtain constrained movement, which is cumbersome,
and secondly, it makes the feature a little less discoverable. In the
Node tool the Ctrl modifier alone also has a certain meaning, and it
is also related to constrained movement (as is generally the case in
Inkscape), so my personal opinion is that the analogy is still there
and we should leave it as it is. But I'm open to different opinions.
What do other people think?

Max

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel