I test on Cubietruck and Radxa Rock Android with a desktop keyboard. The KEY() command only works for some keys. I'd like to use WASD but not all work but the arrow keys do. :blink:
Is this a bug or is there another method?
Yes, it has been a problem for a while now...
:'( Okay then I'll just use what is available for now.
has allways been that and you wont see a fix anytime soon. This due glbasic uses api-8, which is unsupported for SOURCE_KEYBOARD tag in Java. SOURCE_KEYBOARD require a least api-9.
Im was started adding keyboard support, but seen its was never finished.... Not sure im will do that, better to checkout the GameController support.
What is AE? I should get least get a generic USB gamepad for now. I'll try to have settings for controls but keys wsad are pretty important. :(
Android Extras. There do require some fair of work here. But checkout the sticky thread. There is info there.
Howover im have very rare see a keyboard for Android anyway, so its not a issue really. im doubt 99% of users ever could uses that. If they have something physical, its a gamecontroller, not a keyboard. Also Keyboards is NOT supported as gamecontrollers. That due im did have for many issues with it generally in Android and when tried to detecting the names.
Oh I have checked out the AE and there's only general code that scans all keys that I used to test with. :-[
but parsing can been quite annoying, when there is many keys, so its need a better way, so that can been why im dident look on that. But im did do remove keyboard support for gamecontroller. Its was simply too fuzzy to detect it correctly and then dropped it again. Android here can been quite very annoying.
Im do have seen its have never have very good keyboard support anyway.
In addition, most Android devices have no keyboard - if possible you need to organise your control method so that it either uses the accelerator or mouse presses...
That why I'm dropped it again, it's was not feasible support it's fully. But using game controller is much better. But not all have them, so don't forget touchscreen controls. It's the only way on android. So it's a bug there might not been fixed.
I'm did tried that with we, but without success.