Just wondering, how does the interface work for mobile? Is it like the mouse? Any good tutorial on how to use it? The name of some function I could find in the API would be welcome as well.
Currently, both iOS and Android versions map single touch events to the mouse module and accelerometer info to the joystick one.
Only multi-touch events will need to be handled separately (events are sent the orx way for all of them).
In any case, I'd try to use the orxInput module as much as possible as it provides a nice abstraction layer and allow to plug things behind the scene depending on the actual platform used or allowing to trigger inputs programmatically (mapping optinoal buttons from config with no code, remapping all the controls easily, either interactively or in config files, tutorial inputs, etc...).
Comments
Only multi-touch events will need to be handled separately (events are sent the orx way for all of them).
In any case, I'd try to use the orxInput module as much as possible as it provides a nice abstraction layer and allow to plug things behind the scene depending on the actual platform used or allowing to trigger inputs programmatically (mapping optinoal buttons from config with no code, remapping all the controls easily, either interactively or in config files, tutorial inputs, etc...).