However, the viewport window in the editor, as well as keyboard shortcuts like T/R/S, seem to sometimes respond to mouse and keyboard events from the primary window, when the editor window is not in focus.
From experimentation, it seems like the most consistent way to trigger this bug is to put one window over the other and quickly move the mouse from the editor window to the primary window, where the cursor is over one of the two Bevy's windows for every frame, and then try the inputs.
I assume the input code there isn't checking if the window the editor is on is actually in focus before processing input events or something?
I'm adding this editor by slapping it on the Bevy app like so:
However, the viewport window in the editor, as well as keyboard shortcuts like T/R/S, seem to sometimes respond to mouse and keyboard events from the primary window, when the editor window is not in focus.
From experimentation, it seems like the most consistent way to trigger this bug is to put one window over the other and quickly move the mouse from the editor window to the primary window, where the cursor is over one of the two Bevy's windows for every frame, and then try the inputs.
I assume the input code there isn't checking if the window the editor is on is actually in focus before processing input events or something?