You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying out the new ModalScreen, and found some issues when adding an Input widget to it. The arrow keys no longer move the cursor left or right, backspace doesn't do anything, and the enter key does not fire the Input.Submitted event. But regular keystrokes still work to add characters to the input. Putting an Input on a regular Screen doesn't have the issue.
Second related issue - in the example below, when using the enter key to activate the button and pop the screen, the enter key event trickles down to the screen underneath. And because it has 'enter' as the key binding to bring up the dialog, it just pops it right back up. Adding event.stop() to the button handler doesn't stop the key event. The obvious solution is to not use 'enter' to bring up the dialog, but I could see this causing other unintended behavior in other applications too. (This happens on both Screen and ModalScreen.)
I've been trying out the new
ModalScreen
, and found some issues when adding anInput
widget to it. The arrow keys no longer move the cursor left or right, backspace doesn't do anything, and the enter key does not fire theInput.Submitted
event. But regular keystrokes still work to add characters to the input. Putting anInput
on a regularScreen
doesn't have the issue.Second related issue - in the example below, when using the enter key to activate the button and pop the screen, the enter key event trickles down to the screen underneath. And because it has 'enter' as the key binding to bring up the dialog, it just pops it right back up. Adding
event.stop()
to the button handler doesn't stop the key event. The obvious solution is to not use 'enter' to bring up the dialog, but I could see this causing other unintended behavior in other applications too. (This happens on bothScreen
andModalScreen
.)The text was updated successfully, but these errors were encountered: