setMode() doesn't affect touch()

pobtastic

As setMode() alters the resolution of the framebuffer, I'd expect that touch() should then reflect that change? Instead, still refers to the default resolution meaning that it doesn't correspond with what's being drawn on the screen.

PB____

I notice the same applies when using setView(left, top, right, bottom).

If this does get changed, then I think it's helpful that the returned coordinates already are vectors with float values (so the precision doesn't need to be reduced to the used view and/or mode).

spikey

Same here, if you use setMode(1920, 1080) the touch keyboard generates the wrong characters. https://fuzearena.com/forum/topic/1321/touch-keyboard-is-returning-numbers-instead-of-letters

Willpowered

Thanks for the report! I put it on my list of things that need looking at. You can expect a fix in the next patch, because this is a big issue for the touchscreen.

Not 100% sure if these will work, but as possible temporary workarounds:

(First problem) Convert the touch coordinates to the range of your current mode
(Keyboard problem) Before calling input, try setting the mode to 1280x720 and the view to 0, 0, 1280, 720, and change back after