Replies: 3 comments
-
|
Pretty much yes? You can use though the Yes, the input is usually from the press. Probably should also ignore |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Didn't think about Honestly, I'm not keen on the way |
Beta Was this translation helpful? Give feedback.
-
|
It's gated because it's different on mobile and you just get what you get sometimes and I think providing |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Context: I have a text editing widget which can both be typed into and can match (or rather a higher layer can match) sequences like
Ctrl+C.When my app receives a
KeyboardInput { event, .. }, as I understand itevent.textis the replacement for the oldReceivedCharacter(c). But, when should text be input in the text editing widget?event.state == Pressed, otherwise you get duplicate keysControlis pressed ...So, should the widget accept input when
event.state == ElementState::Pressed && self.modifiers.difference(ModifiersState::SHIFT).is_empty()? This appears to work, but I might be missing corner cases.Beta Was this translation helpful? Give feedback.
All reactions