2012-12-03, 10:45
(2012-12-03, 09:36)Montellese Wrote: OK I've had a quick look at this and here is the problem: Let's say xbmc sends a OnInputRequested notification everytime a user focuses an edit control and an OnInputFinished notification when the user unfocuses the edit control. Here is what can happen:It's indeed not trivial. What about this flow:
IMO that's not very intuitive behaviour as you get two OnInputRequested notification and you get an OnInputFinished notification even though you are still in a control that accepts text input. I'm not sure what the best solution would be.
- User focuses edit control -> OnInputRequested notification
- User presses enter -> virtual keyboard dialog opens -> another OnInputRequested notification
- User enters some text and then closes the dialog -> OnInputFinished notification
- User is still focused on the edit control
- User leaves the edit control -> OnInputFinished notification
- User focuses edit control -> OnInputRequested notification
- User presses enter -> virtual keyboard dialog opens -> first send an OnInputFinished because the input control loses focus in favor of the virtual keyboard, and then send an OnInputRequested notification
- User enters some text and then closes the dialog -> OnInputFinished notification
- User is still focused on the edit control; actually the control gets focus again, it was defocused by the virtual keyboard, so send a new OnInputRequested
- User leaves the edit control -> OnInputFinished notification