The power button (Ui.KEY_POWER) doesn't have a mapping in device.xml for the 920XT, and the menu button (Ui.KEY_MENU) only triggers if you hold it down. The necessary changes to bin/devices.xml are pretty simple. Are these issues intentional, and if not, can I expect that my application be able handle short presses of the menu and power buttons?
Additionally, it seems unusual that the Enter button on the 920 results in a call to Behavior.Delegage.onNextPage(), but no key maps to BehaviorDelegate.onPreviousPage(). This essentially forces me to implement the lower-level input handling functionality provided by InputDelegate. Is this an oversight, or is this by design?
Also, are there plans to have the Behavior Delegate or the Input Delegate tell the difference between a short button press and a button hold?
On my 310, I press the lap button to mark a lap and then hold the lap button to do a reset. I don't see how to mimic that functionality easily with the current tools.
Also, are there plans to have the Behavior Delegate or the Input Delegate tell the difference between a short button press and a button hold?
On my 310, I press the lap button to mark a lap and then hold the lap button to do a reset. I don't see how to mimic that functionality easily with the current tools.
We won't have anything for launch as far as key holding. I will add "detecting a reset behavior" in the behavior delegate as a feature request.
