Changing focus and InputScope on DoubleEditBox

I have found a way to prevent the soft keyboard from re-appearing after tapping away from (soft dismiss) of the popup.  

If you create a PopupPickerStyle you can specify what kind of control gets used by the popup, in this you can add in an event handler to one of the elements of the popup and subscribe an event to fire when it gets Unloaded.  This event can be used to redirect focus to a control which does not accept keyboard input, so the soft keyboard won't come back up.  In my case I'm using a button with width and height 0 in order to absorb the focus.

Hi Cody,

The way WinRT popups work is that if you light dismiss them, the focus returns to the previously focused control in the popup owner's visual tree.  WinRT popups don't seem to allow you to tap through to another control immediately while a popup is open.  A second tap is required to focus another control once the popup is dismissed. 

If the control that regains focus upon light dismiss is a text control, the soft keyboard will pop open as needed.  Edit boxes have a TextBox inside their templates and that is what has focus when the edit box gains focus. 

If you set IsEditable = false on an edit box, the TextBox inside its template will be marked read-only and thus the soft keyboard won't show for that edit box, even when it has focus.  The side effect is that text entry won't be available for the edit box while in that mode.  There isn't any way at the moment for you to track when the popup closes other than the manual way you did it.

Another suggestion for this is that you could set the edit box's IsTabStop to true.  Right now it defaults to false, which makes the focus move into the embedded TextBox when it gets focus.  If the edit box's IsTabStop is true, it will be focusable and not pop the soft keyboard when focused, but still will pop the soft keyboard if the embedded TextBox gets focus.

That's a good suggestion for alternate default input scopes on certain edit boxes.  We are changing the numeric, date, and time edit boxes to use Number input scope for the next release.  Also we are exposing a new InputScopeNameValue property on each edit box that will let you customize it further if you like.

Thanks for the feedback, I may have to try the IsTabStop but I think for now attatching events to the template gives us the behavior that we want.

It would also be fairly useful if the various controls had a way to directly assign event handlers to things like OnPopupLoaded or OnPopupDismissed.

Good luck and looking foward to the next version.