After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 341767 - edge resistance should be overridable with a modifier key
edge resistance should be overridable with a modifier key
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
2.20.x
Other All
: Normal minor
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2006-05-14 19:18 UTC by simon80
Modified: 2020-11-06 20:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description simon80 2006-05-14 19:18:10 UTC
I think that the user should be able to disable edge resistance by holding down
either Ctrl, Alt, or Shift while moving the window.  It doesn't matter which
key, but Ctrl makes the most sense given what it does when moving a window with
the keyboard (which is the only override to ER, right now).

Other information:
Comment 1 simon80 2006-05-14 19:22:33 UTC
Another possible override would be to time out the edge resistance, so if the user wants to position a window a tiny bit past an edge, they can wait 1-1.5s (that would be my choice) and if they're still holding onto the window, the edge resistance will disappear and they are free to position the window.  However, I think it is of utmost importance for the user to be able to disable the ER with a modifier, since this covers all situations where the ER intrudes with a simple solution (why a hotkey wasn't included from the start is beyond me).
Comment 2 Björn Lindqvist 2006-05-16 10:29:17 UTC
But you haven't said WHY you want this feature. Describe a use case where this feature would be useful. If it is for pixel-precise positioning of windows, then maybe Alt+F7, ctrl+arrow key would work just as well since it moves the window in increments of one pixel?
Comment 3 simon80 2006-05-16 22:19:58 UTC
It is useful whenever the user wants to position the window precisely in a certain way, like you said.  One example of this is if I want to put a window slightly past the edge of the screen, to save space, or if I'm playing a game and it's running in a window at the same res as my screen, so I want to place it exactly in the middle of the screen, ignoring the borders.  I could do it with the keyboard, like you say, but this is inadequate because it is very slow, and lacks the response of the mouse.

Also, perhaps I'm not sure where I want to put the window, I'd just like the edge resistance to go away because it's triggering for edges that I'm not paying attention to, like if there are many edge triggers in a small area.  Either way, I personally think that there should be a way to disable this with the mouse, intuitively, this is what I would expect if I hold control while moving a window around.  I also think that when using a GUI, there usually should be a way to do something with just the keyboard, and also a way to do it with the mouse, to give people the freedom to use whichever device they prefer.
Comment 4 Olav Vitters 2006-05-16 22:37:58 UTC
For that game reason: Pressing the 'toggle fullscreen mode' shortcut seems far easier. Perhaps even the edge resistance could allow this kind of positioning (window contents excactly as large as screen), without having to use any kind of modifier.
Comment 5 simon80 2007-10-23 08:50:08 UTC
The latest version of metacity uses the shift key to implement some sort of aggressive snapping, while control and alt remain unused.  Being able to do something with the keyboard is not an excuse to omit support for the same action using the mouse.
Comment 6 André Klapper 2020-11-06 20:05:53 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.