View Single Post
Posts: 557 | Thanked: 370 times | Joined on Apr 2010
#370
Originally Posted by Flandry View Post
Any questions?
Nope, none at all... looks like it works just fine. The sed command loses me a little, can't say I've seen it worked that way before, as in splitting so as to use \1 to represent device=...

The main reason I haven't attempted something like this yet is the hopes a GUI will show up out of the blue to do it all for us. As it is I've got a script that accepts 1, 2, 3 as input... copying a specific input profile to blight_input.conf.

While your here, does accelemymote support deadzones? Only the more recent versions of mupen64plus support deadzone on joysticks (from what I have read)

Will almost certainly include this in the next 'release' I do (can hardly call it that when none of it is my work). Hear on the grapevine the next revision of gles plugin isn't far off.


EDIT: Actually, one,
Code:
# ... and not running. Start it up if so...
if [ ! -f /home/user/.accelemymote/live-trigger ]; then
        touch /home/user/.accelemymote/live-trigger
        /opt/maemo/usr/bin/accelemymote &
fi
What exactly is the live-trigger doing here? Simply creating a file with current time so as to know accelemymote is active?

and the & on the end of accelemymote is that passed to the application?

Last edited by IzzehO; 2010-07-08 at 14:37.