-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Removed FocusGained/FocusLost/HasFocus from the BaseEditor. * Every QWidget has a Qt provided `hasFocus()` which the framework automatically handles for us including the focus traversal order. It's extremely rare that you should ever be doing your own custom focus handling in any framework really. https://doc.qt.io/qt-5/qwidget.html#focus-prop https://doc.qt.io/qt-5/focus.html * Removed the `MainWindow::MDIWindowChanged` slot which was handling the custom focus we no longer need. * Removed the custom `_parentHasFocus` member and its setter from the asset scroll area background. * Switched A and D to left/right respectively in the asset scroll area background because they were backwards before. * Allowed the asset scroll area background to handle events when it's not in focus. It's supposed to do this by design because widgets actually need to repaint as another window is moved around on top of them. * The asset scroll area background will not handle events like mouse movement when another MDI window occludes them. The Qt platform does this for us automatically using a mouse trap. Anything else would be _direct_ input, hence the name of DirectInput or raw input. The way GUI frameworks deliver input events after converting them to their own representation is typically by recursing down the tree of widgets starting at the root ancestor window and only delivering the events to the widget where the mouse was actually at. * I verified the above by printing, and it's also behavior I expect from UI frameworks based on my experience with Swing/Qt. * GM 8.1 & LGM have the same expected behavior, the mouse position is updated when not in focus but not if occluded.
- Loading branch information
1 parent
9251834
commit bedf65e
Showing
7 changed files
with
40 additions
and
82 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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