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 it is areas under the mouse that have focus. Extending this to windows feels pretty natural. 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 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 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 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 it is areas under the mouse that have focus. Extending this to windows feels pretty natural. 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.