At least someone having the guts to try my software - thank you for the positive feedback!
Regarding the Win-key, I wouldn't remap it because:
1. I'm using it often
2. The win key is often sent in combination with other keys and it will cause some side effects to remap it - that's why I gave up on this idea
When there's more feedback and some problems discovered that are necessary to change, I will have another look into this FN+Tab issue.
By the way, having Tab remapped to Ctrl also has a good benefit - accidental clicks on tab don't happen anymore.
What can exactly go wrong if you use the windows button? I understand more functions are tied to it, but as a test I remapped it with AE button + and that worked just fine. The windows key now locks my phone. (had to use something to test eh ) and does so every time I press it. Awesome thing is, shift + windows key opens the start menu like it normally does! Don't you think your script could do exactly the same, but then normally map it to ctrl and shift + windows be normal windows? I'd rather use that one as I use tab more often than the windows key.
Also, I understand that your prog can do all that AE button can do; so it can map to functions like tilt the screen. But as there's no UI, how am I supposed to figure out what commands do what? I haven't yet worked with mortscript and my understanding of programming languages is shallow yet sufficient to easily learn how to use it, but I wouldn't know where to begin. For exactly this reason I think the best way to develop this application is two ways combined; a UI with some basic, often-used options as well as an option within that UI to create custom scripted binds, using mortscript. That way you get best of both worlds and every user will be able to use your wonderful code.
The bottomline; I'll tinker with it a bit and you should take JKingDev's offer.