Closed athairus closed 8 years ago
Currently detecting whether to enable "touch mode" by checking for desmume
in two places: The core's path at load time (for QML's use) and in the variable list within LibretroCore
. Maybe a more general approach might be needed?
EDIT: This has changed: Touch mode (which is a QML property of the root window) is now only being set at load time by checking for "desmume" in the core name (string matching). In addition, a simple variable check is done in LibretroCore
: if desmume_pointer_type
exists, set it to touch
.
There's a considerable amount of input lag making high-intensity games difficult to play. It might be intrinsic to MouseArea
and there's nothing we can change about that's so.
We might have to roll our own input code? Maybe SDL can help!
It's very easy to see the input lag with this piece of homebrew (from the libnds examples): http://phoenix.vg/dl/Homebrew/touch_test.nds
Compare Phoenix's performance to RetroArch's. We have some work to do.
Turns out the input lag is almost entirely due to vsync. Since it has nothing to do with how we handle touch input, this bug's done!
GameActionBar
to toggle fullscreen (for DS only?) to compensate for double-click gesture being disabledVideoOutput
to whatever QML input interface we use (compensating for render buffer size unless touch is UV coordinates aka 0.0 to 1.0?)