You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in version: 1.2.14 Reported for operating system, platform: Linux, Other
Comments on the original bug report:
On 2010-11-26 06:30:17 +0000, Jānis Rūcis wrote:
Created attachment 547
Small test program
I had a bug reported against Neverball from some users, saying that in certain situations just after a screen transition the first mouse click does not register, although following clicks do succeed. I could not reproduce it following their instructions on my own system (Debian Lenny), but managed to do so on a virtual install of Ubuntu 10.10.
Here's the original report (FWIW, the code in question has not changed since at least 2004, so any Neverball version is good for testing if you feel like it):
Attached is a little test app to demonstrate the problem. To reproduce it, I used the following set of actions (with mouse clicks interspersed for verbosity):
click
g (grab)
h (hide cursor on next mouse click)
click (hides cursor)
click
h (shows pointer immediately)
click
g (ungrab)
First, here is the (expected) output of the app obtained on Debian Lenny (X.Org 7.3, server 1.4.2):
press
release
grab
hide cursor on next mouse down
press
hide cursor
release
press
release
show cursor
press
release
ungrab
The same set of actions on Ubuntu 10.10 (X.Org 7.5, server 1.9.0):
press
release
grab
hide cursor on next mouse down
press
hide cursor
release
press
release
show cursor
release
ungrab
The mouse down event for the last mouse click is missing.
It seems that what triggers the problem the cursor being hidden between a mouse down and mouse up event (but only when input has already been grabbed earlier or is being grabbed on the same occasion).
The problem also does not occur if SDL_VIDEO_X11_DGAMOUSE is set to 0.
On 2010-11-26 09:11:24 +0000, Jānis Rūcis wrote:
Something I forgot to mention...
I didn't speak much of the SDL versions involved. That's because the two SDL versions I tested (1.2.14 and 1.2.13) were both fine on the Debian system, and were both broken on Ubuntu. So I think the cause lies somewhere in the X.Org server, probably some change that violates assumptions made by SDL.
On 2011-04-12 20:07:57 +0000, Jen Spradlin wrote:
Thank you for your bug report!
We're busy working on getting SDL 1.3 ready for a high quality release, and want to make sure as many things are fixed there as possible.
Could you check to see if your bug is resolved by the latest SDL 1.3 snapshot? http://www.libsdl.org/tmp/SDL-1.3.zip
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Reported in version: 1.2.14
Reported for operating system, platform: Linux, Other
Comments on the original bug report:
On 2010-11-26 06:30:17 +0000, Jānis Rūcis wrote:
On 2010-11-26 09:11:24 +0000, Jānis Rūcis wrote:
On 2011-04-12 20:07:57 +0000, Jen Spradlin wrote:
On 2011-04-13 15:02:08 +0000, Jānis Rūcis wrote:
On 2011-04-13 21:46:48 +0000, Sam Lantinga wrote:
The text was updated successfully, but these errors were encountered: