Hi,

Quoting Justin Gombos :

How do I restrict movement to be either horizontal or vertical?

I tried holding shift, control, and alt, and no luck.

Using the cursors is how I usually handle this. With the move tool selected, Shift selects the active layer rather than the topmost layer underneath the cursor, Control moves a path, and Alt moves a selection (rather than its contents).

When moving a selection with the cursors, Shift-cursor moves the selection by a larger amount (26 pixels, I just checked, no idea why).

Cheers, Dave.

--
Dave Neary
Lyon, France

Hi,

Justin Gombos writes:

How do I restrict movement to be either horizontal or vertical?

Use the cursor keys instead of moving with the mouse. You can press Shift to increase the movement per keypress.

Sven

Hi,

Dave Neary writes:

When moving a selection with the cursors, Shift-cursor moves the selection by a larger amount (26 pixels, I just checked, no idea why).

It moves by 25 pixels. Why? Because it's defined like this in gimpeditselectiontool.c:

#define ARROW_VELOCITY 25

In GIMP 2.1 this behaviour has been changed. The selection is now moved 25 display pixels not 25 image pixels so you get a larger movement if you are looking at the image zoomed out. The behaviour of just using the cursor keys (w/o pressing Shift) didn't change. It always moves exactly one image pixel.

The ChangeLog asked for complaints if anyone dislikes the new behaviour and so far noone complained so it will probably stay this way for GIMP 2.2.

Sven

Hi,

Quoting Sven Neumann :

Dave Neary writes:

When moving a selection with the cursors, Shift-cursor moves the selection by a larger amount (26 pixels, I just checked, no idea why).

It moves by 25 pixels. Why? Because it's defined like this in gimpeditselectiontool.c:

#define ARROW_VELOCITY 25

Odd - I just tried this, and it definitely moves 26 pixels. After 4 moves, the layer is offset 104 pixels, one back to the left, it goes to 78 pixels. This is on Win32, although it seems weird that this would be different from teh windows behaviour...

The ChangeLog asked for complaints if anyone dislikes the new behaviour and so far noone complained so it will probably stay this way for GIMP 2.2.

Not many people are using 2.1 right now (since we discourage binary releases), but I like the change, I think... there will likely be feedback when it's released in a beta though. Plus, very few people read the Changelog, so it's probable the request was missed by most people.

Cheers, Dave.

--
Dave Neary
Lyon, France

On 10 Aug 2004 11:21:12 +0200
Sven Neumann wrote:

It moves by 25 pixels. Why? Because it's defined like this in gimpeditselectiontool.c:

#define ARROW_VELOCITY 25

2.0.4 and 2.1.3 both move 26 pixels

Hi,

Dave Neary writes:

It moves by 25 pixels. Why? Because it's defined like this in gimpeditselectiontool.c:

#define ARROW_VELOCITY 25

Odd - I just tried this, and it definitely moves 26 pixels. After 4 moves, the layer is offset 104 pixels, one back to the left, it goes to 78 pixels. This is on Win32, although it seems weird that this would be different from teh windows behaviour...

Confirmed on Linux. That would be a bug then and should be reported. I suspect that the key event is interpreted twice, once with the modifier (which makes up for 25 pixels) and another time as if the modifier wasn't pressed (which would add another pixel).

Sven