Change Details

On the Windows platform, raise windows and give them focus as the mouse hovers over them. This allows keyboard shortcuts for the area under the mouse without having to click the window caption to make them active. --- This can seem both wonderful and controversial at the same time. This patch makes it so that as you move your mouse between different Blender windows the window under the mouse automatically becomes active - raises and gets focus. And does so all the time and without any user configuration. Note that this only does this when hovering over the //client// portion of the window, not any non-client areas like the caption (titlebar). At first glance this seems non-standard. Auto-raising //between// applications is not common and is generally only an accessibility option. But this is not between applications but only for windows within a single application. And the behavior fits perfectly with the usual Blender behavior that areas under the mouse have focus. Extending this to windows feels pretty natural. I just want to reiterate that this only auto-focuses separate **Blender** windows while the Blender app is active. So this does not change any behavior between Blender and //other// applications. I had plans to make this behavior [[ https://developer.blender.org/D13941 | optional ]], but I'm just not seeing any downside to this. But I don't mind being told otherwise by people testing this. So please try this and give feedback. But please **don't comment unless you actually try this patch** - guesses about the user experience does not help.

On the Windows platform, raise windows and give them focus as the mouse hovers over them. This allows keyboard shortcuts for the area under the mouse without having to click the window caption to make them active. --- This patch makes it so that as you move your mouse between different Blender windows the window under the mouse automatically becomes active - raises and gets focus. And does so all the time and without any user configuration. Note that this is only when hovering over the //client// portion of the window, **not** non-client areas like the caption (title bar). And this is ONLY between separate windows within a single Blender instance, and NOT between Blender and other applications. Even between Blender windows, //not everything// is auto-focused. But most things. Specifically: * Child to parent * Parent to child * Between siblings //of the same parent// * Between main windows //that do not overlap//. The situations where windows are NOT auto-focused are primarily: * main parent windows that overlap each other * between child windows of different parents

On the Windows platform, raise windows and give them focus as the mouse hovers over them. This allows keyboard shortcuts for the area under the mouse without having to click the window caption to make them active. --- This can seem both wonderful and controversial at the same time. This patch makes it so that as you move your mouse between different Blender windows the window under the mouse automatically becomes active - raises and gets focus. And does so all the time and without any user configuration. Note that this only does this when hovering over the //client// portion of the window, not any non-client areas like the caption (titlebar)And does so all the time and without any user configuration. At first glance this seems non-standard. Auto-raising //between// applications is not common and is generally only an accessibility option. But this is not between applications but only for windows within a single applicationNote that this is only when hovering over the //client// portion of the window, **not** non-client areas like the caption (title bar). And the behavior fits perfectly with the usual Blender behavior that areas under the mouse have focus.is is ONLY between separate windows within a single Blender instance, Extending this to windows feels pretty naturaland NOT between Blender and other applications. I just want to reiterate that this only auto-focuses separate **Even between Blender** windows while the Blender app, //not everything// is activeuto-focused. So this does not change any behavior between Blender and //other// applicationsBut most things. Specifically: * Child to parent * Parent to child * Between siblings //of the same parent// * Between main windows //that do not overlap//. I had plans to make this behavior [[ https://developer.blender.org/D13941 | optional ]], but I'm just not seeing any downside to this. But I don't mind being told otherwise by people testing this. So please try this and give feedback. But please **don't comment unless you actually try this patch** - guesses about the user experience does not help.The situations where windows are NOT auto-focused are primarily: * main parent windows that overlap each other * between child windows of different parents