Keymapper problem on S7800

[Stuart Paterson]

Hi,

I'm seeing something strange on my S7800 with your keymapper (version-wise, I installed it yesterday December 4th - from the play store.) Not sure if it's S7800-specific in any way...

I've created a Tincore profile for an N64 emulator, and I've enabled "auto-profile" and ""autohide". As well, I've turned on "show touches" in the Android developer settings. When I start the N64 emulator, I see that the proper profile is loaded, and from the touches being shown, I see that the buttons/controls are registering. The problem is, the left analog stick and D-Pad aren't working correctly.

What I'm seeing is this: No matter what direction I push on the joystick, a white "show touches" circle appears in the center of the joystick icon (where the "stem" of the physical joystick would be). No matter what direction I push it in, a white touch-dot just shows up in the center (rather than going in the direction I'm pressing.) The same goes for the D-Pad. I have the D-pad configured as a touchpad, and positioned overtop of the 4 yellow N64 buttons (the "C" buttons I think they're called), but no matter what direction I press the D-pad, I just see a white dot in the center between the 4 buttons.

I discovered that if I call up the keymapper UI and click on the check mark beside the profile name, it fixes things, and the joystick and D-pad start registering properly.

Am I launching things correctly? I'm assuming this is a bug and the profile should auto-launch in the background and be functional and enabled without having to call up the UI and click on the checkbox? Thoughts? It only seems to happen on the initial loading of the profile.

If there's anything I can do to help, please let me know.

Thanks!

[Tincore.]

Hi,

Thanks for taking your time to report this.

This is not a bug. It is a feature :-)

Autolaunch starts always paused. You need to apply the first profile to activate the mapper.

[Stuart Paterson]

Ah, ok. 

Can I ask why it operates this way? Wouldn't it be good to have it active when it autolaunches? (more transparent to the user). You'd just launch an app, tincore would load the appropriate profile and be operational, no intervention required from the user... 

[Stuart Paterson]

Any chance of a quick explanation as to why the mapper starts paused on autolaunch?

Thanks!

[Tincore.]

I will look it but I consider it risky.

I prefer that the user confirms the loaded profile.

[Stuart Paterson]

Ah, so you're concerned about risk? In the sense that it might take over control of things? 

I hadn't thought about that (like I said, I was just wondering what your thoughts were). Perhaps a pre-profile option "auto-enable on auto-load"? Or maybe you're right and it's best to leave it as is... hmm...