People, seriously stop it with the Nunchuck+Wiimote thing.
If you want to play FPS and Racing NGC games with those, you are fine with the abundant range of controllers you have available right now.
Programming IR in conjuction with the app is a severe pain in the ass, I know for sure since one of my school projects was based on that, and to get the pointer to be smooth and responsive is quite a hard task even with a simplistic tool as GlovePIE.
I say just drop dead with that topic, leave it be dead for now since it is not important right now.
Now that the most requested features are supported (Bluetooth and Audio Streaming) the next would be compatibility and some code clean.
Other major features might come after that, but seriously stop asking about Nunchuck.
FIX94 already said he has no interest in adding that feature now, and I respect that decision and support it.
Out of that, about the Digital/Analog triggers MOD I've been working on...
Rob Blou already pointed me in the right direction.
The code I made WAS CORRECT, I did get analog values out of pressing L+ZR, and if I let go the L button the controllers reacts with a Full Press.
The problem here is,
Rob Blou said that in his controller.ini, he had two different offsets for the Analog Triggers to work on a Digital button controller.
L=3,01 and R=3,02 are the values he has in his controller ini along with offsets 12 and 13 for the 00 - FF range.
The values 01 and 02 are the ones that indicate exactly WHEN the triggers are being fully pressed.
In the Bluetooth code, we have the 02 value enabled by default, so it doesn't matter if you have FF or 00 in the code, it will ALWAYS make Mario stop because the 02 value is always enabled.
Now I gotta search for that particular part of the code that works with such value and see if I can "disable it" in the L+ZR/ZL combo, and then let it be enabled in the sole press of ZR.
Well then, gotta start looking for that offset and 02...