Don't know if this is just an android client issue, or me that couldn't find the proper configuration…
When I press a key it doesn't make anything, only when I release it…
This prevents from implementing things like Fast Forwarding or keeping an arrow key pressed.
I'd like an option to enable keyboard, but this sort of conflicts with executing several commands by pressing one key…
So I thought:
Add a configuration parameter to enable long press for specific keys, and:
a) If a key keeps being down, after a time threshold send several times the same command.
or
b) Implement a different set of commands for long pressed keys.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
android client should send events on both press/release. But it is true, it does not send
events if user keeps an button pressed.
I'm going to think about that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't know if this is just an android client issue, or me that couldn't find the proper configuration…
When I press a key it doesn't make anything, only when I release it…
This prevents from implementing things like Fast Forwarding or keeping an arrow key pressed.
I'd like an option to enable keyboard, but this sort of conflicts with executing several commands by pressing one key…
So I thought:
Add a configuration parameter to enable long press for specific keys, and:
a) If a key keeps being down, after a time threshold send several times the same command.
or
b) Implement a different set of commands for long pressed keys.
android client should send events on both press/release. But it is true, it does not send
events if user keeps an button pressed.
I'm going to think about that.
For what I undestood, the relevan code is commented in the sources.