Repository navigation
Conversation
…m inside the event loop (a native menu's item)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For a native menu bar whose items do what their key equivalents do. A menu item fires inside the event loop, and the key it takes never reaches the window. The program's own native code can call
crate::window::inject(kind, code, mods)to hand the program the same input instead.The inputs go to a thread-local queue apart from the host, because the host is borrowed while the loop runs. They join the window with the focus (else the current one) after each pump, and the loop is woken.
Checked: an injected TEXT 'c' with Super arrives after the window's FOCUS event, as kind 5, code 99, mods 8, window 1.