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 612822 - Allow disabling of edge snapping/resistance
Allow disabling of edge snapping/resistance
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2010-03-13 21:35 UTC by Nathaniel Gephart
Modified: 2020-11-07 12:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Implements the option to disable edge resistance. (2.97 KB, patch)
2010-04-03 01:17 UTC, Nathaniel Gephart 		rejected Details | Review

Description Nathaniel Gephart 2010-03-13 21:35:03 UTC 
There are a number of bugs open related to this, but none that addresses this issue specifically (so far as I've seen). I find edge snapping/resistance to be annoying in all cases. I propose adding an option to disable it entirely.
Comment 1 Nathaniel Gephart 2010-04-03 01:17:20 UTC 
Created attachment 157783 [details] [review]
Implements the option to disable edge resistance.
Comment 2 Thomas Thurman 2010-05-08 21:42:22 UTC 
Review of attachment 157783 [details] [review]:

The patch looks fine, but I can't see us adding an option for this sort of thing.  Thanks for providing it, though: the distros might want to pick it up.
Comment 3 André Klapper 2020-11-07 12:36:15 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all
old feature requests in Bugzilla which have not seen updates for many years.

If you still use metacity and if you are still requesting this feature 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 implemented.