Bug 140595 - Alt+Drag cannot be used in GIMP by default
Alt+Drag cannot be used in GIMP by default
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: metacity (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-23 14:28 EST by Matthew Mott
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-23 18:04:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Matthew Mott 2004-11-23 14:28:51 EST
Description of problem:
To move a selection in GIMP one uses the Alt key plus mouse dragging. This
cannot be used in FC3 since this key/mouse combo is intercepted by
GNOME/Metacity to move the window. This option must be set to "Meta" in
Preferences -> Window in order to allow GIMP to work properly, and the option
"Hyper is mapped to the Win keys" must be set in Preferences -> Keyboard as well.

Version-Release number of selected component (if applicable):
metacity-2.8.6-2

How reproducible:
Always, if default config is used.

Steps to Reproduce:
1. Make a selection in GIMP
2. Try to move the selection by Alt-dragging
  
Actual results:
The GIMP window is moved.

Expected results:
The selection within GIMP should be moved.

Additional info:
In addition to using "Meta" as the default rather than "Alt", it would be nice
to have an "Off" option in this area, in case it was desired to have all
shortcuts available rather than being used by GNOME.
Comment 1 Matthew Mott 2004-11-23 14:30:12 EST
Correction: the option "Meta is mapped to the Win keys" must be set, not "Hyper
..." This allows the Win keys to be used for window moving, but GIMP shortcuts
work as expected.
Comment 2 Havoc Pennington 2004-11-23 18:04:34 EST
We tried defaulting to hyper for a while, it has other issues.
I don't remember them all honestly but bugzilla.gnome.org should have
old bugs about it.

There's no way to configure the WM to avoid all app collisions since
some app uses every key. The right thing is for GNOME to define the
default keybindings (upstream, never changed by distributions) and for
apps to default to bindings that don't conflict with the desktop.
The thing that most facilitates that is for us to keep the same
bindings and avoid changing them all the time, so apps have a stable
target.

You don't want a situation where app version 2 adapts to desktop
version 1, then desktop version 2 adapts to app version 1, then app
version 3 adapts to desktop version 2, then desktop version 3 adapts
to app version 2, and so forth. Sounds wacky but this is historically
exactly what has happened.

If distributions do something different from upstream GNOME or
upstream apps, it makes the whole thing that much worse with everyone
adapting to everyone else. We need GNOME to stay stable, and
distributions to stick to the defaults.


Note You need to log in before you can comment on or make changes to this bug.