Add exclusive window handling to DisplayServer (on macOS and Windows). #56953
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.
I'm not entirely sure if this is the intended way to handle it.
I assume
exclusive
window should stay on top of it's parent and prevent focusing of the parent, andtransient
just mean it won't exist longer than a parent.There's a limitation with macOS windowing system which (in some configs) prevents "child window" (which always stay on top of the parent) to be on the other screen (or virtual desktop) than its parent window.
Which should be OK for the
exclusive
dialogs (like file open), but is not OK fortransient
windows (e.g., undocked property inspector, etc.).This PR adds function to set
exclusive
mode to theDisplayServer
, changes behavior on Windows to keep onlyexclusive
children windows on top of the parent (instead of alltransient
), and adds the same functionality to the macOS.Fixes #57152
Fixes #57831