Add Mouse Support

[popeyeotaku]

Add Mouse Support

[megamarc]

Hi @everyfan, assisted mouse support was introduced in release 1.21, exposing the underlying SDL2 events to tilengine with the SDL_SetSDLCallback function. This API function is briefly documented but easy to use, and there's a fully working example in the main repository: https://github.com/megamarc/Tilengine/blob/master/samples/TestMouse.c.
You'll need the SDL2 development headers because the example interfaces directly with the SDL2 library.

Hi Marc.

I have a problem with this, it has to do with the window factor.
In TestMouse.c

#define WIDTH 400  // I only take the width to simplify

Next, Window.c

Tilengine/src/Window.c

Line 180 in dd88613

wnd_width = wnd_params.width*factor;

wnd_width = 400 * 3;  then wnd_width equal to 1200

The SDL_Mouse coordinates correspond to the window(w=1200), not the sprite(x= 180 y=166)
The solution is simple, get the factor and then divide that factor to the mouse coordinate:

If Window.c

 factor = 3

Then TestMouse.c

if (entity->enabled &&
 mouse->x / factor >= entity->x && mouse->y / factor  >= entity->y &&

Is it possible to change the API, to return the factor, or better, to transform a coordinate according to the factor?

[popeyeotaku]

Also, I have never found a way to implement the mouse system you describe using the pysdl2 bindings

…

On Sun, Feb 3, 2019, 2:03 PM Daniel T. Borelli ***@***.*** wrote: Hi Marc. I have a problem with this, it has to do with the window factor. In TestMouse.c #define WIDTH 400 // I only take the width to simplify Next, Window.c https://github.com/megamarc/Tilengine/blob/dd886131d62cddcac2069c1d9801d5ef5810567f/src/Window.c#L180 wnd_width = 400 * 3; then wnd_width equal to 1200 The SDL_Mouse coordinates correspond to the window(w=1200), not the sprite(x= 180 y=166) The solution is simple, get the factor and then divide that factor to the mouse coordinate: If Window.c factor = 3 Then TestMouse.c if (entity->enabled && mouse->x / factor >= entity->x && mouse->y / factor >= entity->y && Is it possible to change the API, to return the factor, or better, to transform a coordinate according to the factor? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AM2QljO7d79W3zFrCGSSJacfs49yaiYBks5vJzJvgaJpZM4Xa3_z> .

[megamarc]

@daltomi: of course that's a bug! Thanks for pointing it. I'll fix it. Mouse input should return the coordinates in framebuffer space, not in window space. Window scaling factor shouldn't affect the returned value.
@everyfan: the SDL2 bridge to handle events is implemented into the main library, but not into the python binding.