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 649797 - Add edge resistance between screens when dragging windows
Add edge resistance between screens when dragging windows
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: mutter-maint
mutter-maint
: 685961 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-05-09 14:22 UTC by Will Thompson
Modified: 2021-07-05 13:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Will Thompson 2011-05-09 14:22:37 UTC
I'm really enjoying split-screen tiling of windows in Shell. However, when I'm at my desk, I have two screens, and hence have to aim very precisely to tile on the left of the right-hand screen and on the right of the left-hand screen. Coupled with the half-second(?) delay between dragging a window to the right region and the blue box appearing, this is a bit of a pain.

It would be nice if there were resistance to the pointer crossing between screens, akin to the existing resistance when the edge of the window hits the edge of the screen, but perhaps a little stronger.
Comment 1 Rui Matos 2011-05-09 14:32:24 UTC
(In reply to comment #0)
> It would be nice if there were resistance to the pointer crossing between
> screens, akin to the existing resistance when the edge of the window hits the
> edge of the screen, but perhaps a little stronger.

Maybe you assumed this but, to make it explicit, the resistance should only be applied while a window is being dragged, right?
Comment 2 Will Thompson 2011-05-09 16:10:59 UTC
(In reply to comment #1)
> Maybe you assumed this but, to make it explicit, the resistance should only be
> applied while a window is being dragged, right?

Exactly.Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 3 Will Thompson 2011-05-09 16:11:58 UTC
(what on earth? how did I manage to do that?)
Comment 4 Debarshi Ray 2014-06-26 13:18:32 UTC
*** Bug 685961 has been marked as a duplicate of this bug. ***
Comment 5 GNOME Infrastructure Team 2021-07-05 13:47:25 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.