[BUG] SDL_GetMouseState ≠ SDL_MouseButtonEvent

krux · August 7, 2014, 10:41pm

SDL_GetMouseState and SDL_MouseButtonEvent have a different coordinate system for the mouse position. When my logical size matches the window size, both work fine, but when my logical size is smaller then my window size, then the event gives me coordinates in logical size coordinates and SDL_GetMouseState gives me unscaled window coordinates.

krux · August 10, 2014, 4:34pm

sorry if I repost here to just bring this topic to the top again. But I think this is really a major bug that can be fixed easily. So pleas any response. And sorry for the unprintable not equals sign in the title, didn’t know that this board replaces it with something that is displayed wrongly everywhere.

Daniel_Gibson · August 15, 2014, 5:26pm

Sounds like a bug to me, did you create an issue in
https://bugzilla.libsdl.org/ ?

Cheers,
DanielAm 08.08.2014 00:41, schrieb krux:

SDL_GetMouseState and SDL_MouseButtonEvent have a different coordinate
system for the mouse position. When my logical size matches the window
size, both work fine, but when my logical size is smaller then my window
size, then the event gives me coordinates in logical size coordinates
and SDL_GetMouseState gives me unscaled window coordinates.

slouken · August 20, 2014, 5:12am

What would be your preferred solution for this?On Sun, Aug 10, 2014 at 9:34 AM, krux <arne.doering at gmx.net> wrote:

sorry if I repost here to just bring this topic to the top again. But I
think this is really a major bug that can be fixed easily. So pleas any
response. And sorry for the unprintable not equals sign in the title,
didn’t know that this board replaces it with something that is displayed
wrongly everywhere.

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Leonardo_Guilherme · August 20, 2014, 12:52pm

There’s a bug in the bugzilla for this issue already:

github.com/libsdl-org/SDL

SDL_GetMouseState() seems to give raw mouse position when using SDL_RenderSetLogicalSize()

opened 11:31PM - 10 Feb 21 UTC

closed 02:42AM - 18 Dec 21 UTC

SDLBugzilla

# This bug report was migrated from our old Bugzilla tracker. These attachmen…ts are available in the static archive: * [shows bug (mousestate.c, text/x-csrc, 2014-03-11 01:54:46 +0000, 852 bytes)](https://bugzilla.libsdl.org/attachment.cgi?id=1589) **Reported in version:** HG 2.1 **Reported for operating system, platform:** Linux, x86_64 # Comments on the original bug report: On 2014-03-11 01:41:25 +0000, wrote: > As summary. MOUSEBUTTONDOWN events report the position as expected (in logical screen coordinates). The window is resizable. Probably also happens with fixed-size windows and a logical size that is a different aspect ratio than the window itself. On 2014-03-11 01:54:46 +0000, wrote: > Created attachment 1589 > shows bug > > Here is an example program that shows the bug. On my machine, clicking in the corners of the white rectangle: > > ``` > $ ./mousestate > MOUSEBUTTONDOWN (1, 2) > GetMouseState (102, 3) > > MOUSEBUTTONDOWN (398, 398) > GetMouseState (697, 598) > ``` On 2014-05-10 15:13:51 +0000, Leonardo wrote: > This is true. The problem is that GetMouseState() consults the x/y directly whereas when reported via events, the renderer changes all the mouse events first with an event watcher before they go to the queue. > > I don't see this being fixed easily as it would require the GetMouseState function to consult the renderer. > > Actually this can come in handy if you ever need the real mouse position as there is no other way of knowing it. If you require your mouse coordinates to be adjusted to the logical size, you can create a event watcher like this: > > ```c > int MouseWatcher(void* userdata, SDL_Event* event) { > MouseState * m = (MouseState*) userdata; > switch(event->type) { > case SDL_MOUSEBUTTONDOWN: > case SDL_MOUSEBUTTONUP: > m->x = event->button.x; > m->y = event->button.y; > break; > case SDL_MOUSEMOTION: > m->x = event->motion.x; > m->y = event->motion.y; > break; > default: > break; > } > return 0; > } > ``` > > And then add it: > > ```c > { > SDL_AddEventWatch(MouseWatcher, mouseState); > } > ``` > > Note that you'll need at least 2.0.3 because of bug # 2414 On 2014-07-09 07:09:03 +0000, Sylvain wrote: > Hey, I am not the original poster but I faced the same issue. > Just some thought: > > CreateRenderer assume a Window. > But could we created several Renderer for the Same Window? > > If so, converting an "event" (mouse position) from Window Frame to Renderer Frame is king of buggy, we could only convert to 1 specific Renderer Frame (or to the only renderer if only 1 one exists). > > If no, maybe we could add a function to get the renderer of a Window : > > SDL_renderer * SDL_GetRendererOfWindow(SDL_window*) > > Also. Maybe the code of "SDL_RendererEventWatch" could be factorized to have a function like : > > "convert_event_in_window_coordinates_to_renderer_coordinates" > > We would be used in SDL_RendererEventWatch, and also exported so that users who call SDL_GetMouseState can convert their event to LogicalRendererSize. > > Cheers, > > Sylvain On 2015-01-09 20:55:05 +0000, wrote: > It seems to me the resolution of this is just to add Leonardo's comments to the docs/wiki. Right now it doesn't say that SDL_GetMouseState() is the only way to get the real mouse position. In light of that, it makes sense to just get the computed position from the motion or button events. On 2016-06-09 03:02:31 +0000, Arne Döring wrote: > I would like to ask, if there is anything done on this bug? I found out about this bug, too, and because the logical size didn't even do a recalculation of the mouse coordinates, I decided, to not use the logical size anymore. I really feels like a not well thought through feature, that I wouldn't recommend to anyone who uses SDL. > > But the not make this post sound too negative. Thanks for the great work to have SDL2 actually done. I enjoy working with it. On 2019-10-17 11:45:16 +0000, Sylvain wrote: > It's reasonable to say that querying the state returns raw values,! > We can revisit this for SDL 2.1 > (see also bug 4028)

You could work around it by using event handlers, as the renderers fixes
the mouse events according to its logical size.

I don’t know how should we go because getting the true mouse coordinates
can be useful…? Maybe through another function, say,
SDL_GetAbsoluteMouseState(), to make it clear.

2014-08-20 2:12 GMT-03:00 Sam Lantinga :> What would be your preferred solution for this?

On Sun, Aug 10, 2014 at 9:34 AM, krux <arne.doering at gmx.net> wrote:

sorry if I repost here to just bring this topic to the top again. But I
think this is really a major bug that can be fixed easily. So pleas any
response. And sorry for the unprintable not equals sign in the title,
didn’t know that this board replaces it with something that is displayed
wrongly everywhere.

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

[BUG] SDL_GetMouseState &#8800; SDL_MouseButtonEvent

[BUG] SDL_GetMouseState ≠ SDL_MouseButtonEvent