Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Window movement to be initiated by Wayland clients (Fixes #61) #171

Merged
merged 4 commits into from
Feb 19, 2018

Conversation

AlanGriffiths
Copy link
Contributor

  1. Connects up Wayland move() requests with the CSD move support.
  2. Implements move in the "floating" window manager
  3. Consolidates the move logic

NB GTK apps on Artful don't work with this but Qt apps and weston-terminal do.
(On Bionic, Fedora 27 and rawhide GTK apps seem fine.)

@AlanGriffiths
Copy link
Contributor Author

I know we also need to implement CSD move support in the tiling WM, but that's something for next week.

@gerboland
Copy link
Contributor

Works well. One bug I've spotted though, not sure if it is compositor or client:

  1. open QtCreator
  2. Move mouse to the title bar, just over one of the menubar items (e.g. Debug)
  3. Mouse down, and then move mouse up a bit
    I see the menubar seems to respond to a mouse hover event, while the window is being dragged up a little (looks like if you move menubar entry to location where initial mouse-down occurred, that entry acts like the mouse is hovering over it)

I'm upgrading to bionic to try GTK to see if it has the same issue.

@AlanGriffiths
Copy link
Contributor Author

@gerboland yes, this is a problem. The trouble is we have recently landed some code that synthesises cursor move events to a surface that moves under the cursor.

That code doesn't consider the possibility that the cursor and surface are moving together. And the synthetic events are not routed through the WM policy which "eats" other pointer events during the move.

I move we land this (as being an improvement) and raise an issue about the synthetic events.

Copy link
Contributor

@gerboland gerboland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy to land this so
bors r+

bors bot added a commit that referenced this pull request Feb 19, 2018
170: De-dup Cookie handle class r=gerboland a=AlanGriffiths



171: Allow Window movement to be initiated by Wayland clients (Fixes #61) r=gerboland a=AlanGriffiths

1. Connects up Wayland move() requests with the CSD move support.
2. Implements move in the "floating" window manager
3. Consolidates the move logic

NB GTK apps on *Artful* don't work with this but Qt apps and weston-terminal do.
(On Bionic, Fedora 27 and rawhide GTK apps seem fine.)

177: Bump the libmirserver sonumber r=gerboland a=AlanGriffiths

We've broken ABI by changing SurfaceObserver. Bump the library version to match.
@bors
Copy link
Contributor

bors bot commented Feb 19, 2018

Build succeeded

@bors bors bot merged commit 3348e20 into master Feb 19, 2018
@bors bors bot deleted the csd-move branch February 19, 2018 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants