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
It seems that current TS code for Pandora(not SDL_INPUT version) reports TS coords of the physical screen, and thus, if the application doesn't use the full 800x480 screen in fullscreen, the coords are wrong!
SimpleJoy needs to compensate for Window offset on screen and for lower than 800x480 resolutions!
The text was updated successfully, but these errors were encountered:
Is that maybe related to this: http://blogs.distant-earth.com/wp/?p=293 (and thus can be fixed by the workaround described there).
I recall LemmingsSDL (using a 640x480 resolution) had the same problem when one moved the cursor outside the bounds of the app, but it was nicely fixed by the above workaround.
Well this fix also needs applying, but this is actually a different bug.
This bug is related to tslib. Calaculating the screen position from the raw
data only gives us the physical screen position. The code doesn't compensate
for window placement and lower resolution.
The bug you are linking is where the cursor drifts in SDL, so equally
important to fix but not the same! :)
Is that maybe related to this: http://blogs.distant-earth.com/wp/?p=293(and thus can be fixed by the workaround described there).
I recall LemmingsSDL (using a 640x480 resolution) had the same problem when
one moved the cursor outside the bounds of the app, but it was nicely fixed
by the above workaround.
Reply to this email directly or view it on GitHub: #2 (comment)
Kevin Winfield-Pantoja,
Pirate Games - pirategames.co.uk
It seems that current TS code for Pandora(not SDL_INPUT version) reports TS coords of the physical screen, and thus, if the application doesn't use the full 800x480 screen in fullscreen, the coords are wrong!
SimpleJoy needs to compensate for Window offset on screen and for lower than 800x480 resolutions!
The text was updated successfully, but these errors were encountered: