[kwin] [Bug 386954] Pointer locking/confinement issues

2018-02-08 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #14 from Yannick  ---
The issue is still here with Plasma 5.12.0.

When I start Neverball with both the X11 and Wayland SDL backends, pressing
"Escape" in the game will not unlock the cursor.
I have to Alt+tab out or press "Escape" during 3 seconds to unlock it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2018-01-04 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #13 from Yannick  ---
I applied the patch on top of Kwin 5.11.5.
I'm not sure if it's the right thing to do, but building kwin-git and all its
*-git dependencies would take ages on my computer.

I still had issues with Neverball and Xonotic. The pointer is not unlocked when
I press Escape on Neverball, and is often not properly confined to the Xonotic
in-game menu.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2018-01-03 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954

Martin Flöser  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kwi
   ||n/6ab625ed9770feae1924f4396
   ||9ea63c5ef5ef0f5
 Resolution|--- |FIXED

--- Comment #12 from Martin Flöser  ---
Git commit 6ab625ed9770feae1924f43969ea63c5ef5ef0f5 by Martin Flöser.
Committed on 03/01/2018 at 20:15.
Pushed by graesslin into branch 'master'.

Ignore outputOnly QWindows for pointer and touch events

Summary:
The idea is to be output only, so also ignore for pointer and touch.
This is similar to the previous commit for keyboard events.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D9647

M  +3-0input.cpp

https://commits.kde.org/kwin/6ab625ed9770feae1924f43969ea63c5ef5ef0f5

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2018-01-03 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954

Martin Flöser  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D9647
  Flags||ReviewRequest+

--- Comment #11 from Martin Flöser  ---
Possible patch at: https://phabricator.kde.org/D9647

I'm quite confident it fixes the issue, but I haven't tested yet. If you have a
chance to test I would appreciate it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2018-01-02 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #10 from Martin Flöser  ---
I found a potential issue in KWin. It might be that the OSD is stealing pointer
events.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-16 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #9 from Martin Flöser  ---
It might be that XWayland assumes a bug in the Wayland compositor. I read the
documentation of pointer locking again and looked at the source code of
XWayland and that doesn't fit. We have in the protocol:

"If the client is drawing its own cursor, it should update the position hint to
the position of its own cursor. A compositor *may* use this information to warp
the pointer *upon unlock* in order to avoid pointer jumps."

So KWin can ignore this hint (and does so) and it should only use it on unlock.
But XWayland has a xwl_pointer_warp_emulator_set_fake_pos which uses the hint
described above. I'll further investigate, but I think XWayland is built
against the behavior of Weston and not against the spec.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #8 from Yannick  ---
I tried Neverball and Xonotic on a Weston session, and didn't have any of the
problems I encountered with Plasma.

The pointer is correctly locked/unlocked on Weston.

I made sure to run both games with the X11 SDL backend (SDL_VIDEODRIVER=x11).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #7 from Martin Flöser  ---
the other problem is the locking. Well, that looks like an xwayland bug to me.
Obviously the mouse doesn't move when locked. That's the idea behind it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #6 from Martin Flöser  ---
Ok, I just installed neverball to see what's going on. The main problem is that
neverball acts on repeated key press events for escape key and do to that the
breaking of the confinement doesn't work correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #5 from Yannick  ---
Sorry, my bad:

I made another test with Neverball. When I press "Escape", the mouse pointer
remains visible. It just won't move.

I noticed a few more things:
 - I can also unlock the pointer on Neverball by pressing Alt+Tab a few times.
 - As long as the OSD is visible, no game input is taken into consideration
(for example, I can't use Escape to exit Neverball or Space/right click to jump
into Xonotic action).
 - When I quit Xonotic, the mouse cursor remains locked on the desktop.
Pressing Escape during 3 seconds unlocks it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #4 from Yannick  ---
Hi,

1. I use xorg-server-xwayland 1.19.5
2. There should be a mouse cursor on the neverball screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386954

Martin Flöser  changed:

   What|Removed |Added

  Component|wayland-generic |input
  Flags||Wayland+, X11-

--- Comment #3 from Martin Flöser  ---
I have a few questions:
1. what's your exact xwayland version?
2. what is the screenshot of neverball supposed to show me?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #2 from Yannick  ---
I am aware that the issue with NetRadiant is not easily reproducible, because
this application is quite specific and requires a special setup, sorry for that
:(

But maybe other applications have the same usability issue (it's probably the
case for other *radiant forks like GTKRadiant).

I tried Blender and it worked fine, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386954] Pointer locking/confinement issues

2017-11-15 Thread Yannick
https://bugs.kde.org/show_bug.cgi?id=386954

--- Comment #1 from Yannick  ---
Created attachment 108881
  --> https://bugs.kde.org/attachment.cgi?id=108881&action=edit
NetRadiant layout, with 3D and 2D views

-- 
You are receiving this mail because:
You are watching all bug changes.