We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 89 - mouse and cursor don't agree in X11
Summary: mouse and cursor don't agree in X11
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: don't know
Hardware: x86 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-27 00:20 UTC by Sam Lantinga
Modified: 2006-03-20 00:53 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Lantinga 2006-01-27 00:20:20 UTC
Date: Tue, 10 Feb 2004 09:31:09 -0500
From: Paul Rensing <paul.rensing@att.net>
Subject: [SDL] Bug: mouse and cursor don't agree

I am having trouble with SDL under Linux (specifically Fedora Core 1). I
am running SDL 1.2.5. I see the problem in TuxPaint (a kid's drawing
program) and Frozen-bubbles (when using the mouse).

The problem is that, in fullscreen mode, the location of the mouse and
where the cursor is drawn don't agree. I am running on a laptop, so in
fullscreen mode, the active window is about 1/2 the screen size (screen
is 1024x768; program window is 640x480). The cursor is drawn up and to
the left of where the app thinks the mouse actually is. The offset
appears to be equal to the width/height of the black border.

I see this in two programs, so I believe it is a libsdl problem. I tried
getting SDL 1.2.6 and compiling it myself, but no change. I tried
turning off DGA mode in X; no change.
Comment 1 Sam Lantinga 2006-01-27 00:20:39 UTC
Can anyone confirm that this is active?
Comment 2 Ryan C. Gordon 2006-01-27 11:23:26 UTC
Setting Sam as "QA Contact" on all bugs (even resolved ones) so he'll definitely be in the loop to any further discussion here about SDL.

--ryan.

Comment 3 Sam Lantinga 2006-03-20 00:53:48 UTC
I believe this is long fixed.  Go ahead and reopen it if there are new reports.