[Scummvm-devel] Backend-specific options and when the common launcher isn't the best fit

Angus Lees alees at google.com
Tue Oct 26 14:58:21 CEST 2010


(Changing subjects)

On Tue, Oct 26, 2010 at 23:31, Michael Nicholls <nicholls.mc at gmail.com> wrote:
> This is more a general question, but what is the best way to configure
> different, touchscreen/mouse behaviours?
> I have a mode that differs to the original so switching between the two using
> whatever the correct method is would be preferable.

So far I have no Android-specific config options, which has made
right-click alternatives particularly problematic.

ScummVM folks: what is the right way to add backend-specific options?
I'm led to believe that some of the ports #ifdef in their own options
in the common gui dialogs but I haven't looked at the details - is
that the best/only way?


I dream of being able to replace the launcher with some normal Android
code that used native Android widgets (so they are actually capable of
being clicked on with a fat finger on a small screen, skipping
desktop-centric idioms like double-clicking and tabs, and options I
know don't exist on Android like midi hardware).
If I was to toss the launcher and just call into MetaEngine, etc
directly would that upset lots of people?  I can see that might cause
a support burden for the rest of ScummVM so I understand if it isn't
something you'd want to see in the main ScummVM tree.

 - Gus




More information about the Scummvm-devel mailing list