Window autofocus misbehaves #109886

New Issue

Pootis · 2023-07-10T00:36:05+02:00

Pootis commented

2023-07-10 00:36:05 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79

Blender Version
Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb (from steam)
Worked: Never, this feature only appeared in 3.6.0

Short description of error
Autofocus between main windows works in a weird way: It doesn't autofocus between two fullscreen windows, but does autofocus between one fullscreen window and one windowed. Please see attached video for details as this is hard to describe

Exact steps for others to reproduce the error
You need at least two monitors to replicate this issue: Open Blender -> Create one more main window -> maximize both windows on both monitors and try dragging your mouse between them. It will not autofocus.
Please see the attached video.
I have also attached a photo of my physical setup, just in case.

I did test the latest build (blender-4.0.0-alpha+main.b183e3ae89a6-windows.amd64-release)

Sidenote: It'd be really cool if the autofocus thing was instant, without a one-second delay.

Thank you.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79 **Blender Version** Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` (from steam) Worked: Never, this feature only appeared in 3.6.0 **Short description of error** Autofocus between main windows works in a weird way: It doesn't autofocus between two fullscreen windows, but does autofocus between one fullscreen window and one windowed. Please see attached video for details as this is hard to describe **Exact steps for others to reproduce the error** You need at least two monitors to replicate this issue: Open Blender -> Create one more main window -> maximize both windows on both monitors and try dragging your mouse between them. It will not autofocus. Please see the attached video. I have also attached a photo of my physical setup, just in case. I did test the latest build (blender-4.0.0-alpha+main.b183e3ae89a6-windows.amd64-release) Sidenote: It'd be really cool if the autofocus thing was instant, without a one-second delay. Thank you.

physical_setup.jpg

2.5 MiB

2023-07-10_00-22-14.mp4

2.8 MiB

Pootis added the

labels 2023-07-10 00:36:06 +02:00

Harley Acheson self-assigned this 2023-07-10 04:22:51 +02:00

Pratik Borhade commented

2023-07-10 05:22:58 +02:00

Thanks for the report. Can confirm with split screen option on single monitor.

AFAICS this is happening when window is snapped to screen borders.

Thanks for the report. Can confirm with split screen option on single monitor. AFAICS this is happening when window is snapped to screen borders.

❤️ 1

Pratik Borhade added

and removed

labels 2023-07-10 05:23:18 +02:00

funty commented

2023-07-10 16:45:52 +02:00

On Blender 3.6.0, Windows 10

@MrKleiner

Unless I am missing something here, it works as intended.

Tried it on two monitors and it works with fullscreen windows. Also watched your video, where I can see it is also working with fullscreen windows.

Unless we are noticing different things, in your video your fullscreen windows are responding to you Blender's autofocus. I can see a shade change when you mouse over.

Instead of only noticing the title bars, to confirm use your mouse scroll button to zoom in and out of two fullscreen viewports on two different monitors. Or zoom in and out on your UV editor area, and your viewport in the other monitor. I tried it and it works flawlessly.

On Blender 3.6.0, Windows 10 @MrKleiner Unless I am missing something here, it works as intended. Tried it on two monitors and it works with fullscreen windows. Also watched your video, where I can see it is also working with fullscreen windows. Unless we are noticing different things, in your video your fullscreen windows are responding to you Blender's autofocus. I can see a shade change when you mouse over. Instead of only noticing the title bars, to confirm use your mouse scroll button to zoom in and out of two fullscreen viewports on two different monitors. Or zoom in and out on your UV editor area, and your viewport in the other monitor. I tried it and it works flawlessly.

Harley Acheson commented

2023-07-10 17:20:22 +02:00

@funty - Unless I am missing something here...see a shade change when you mouse over.

What you are seeing is the other window respond to mouse movement and input, but what would not work is keyboard entry and shortcuts. On Windows, keyboard events are only sent to the (one) active window, which you can see gets a different title bar color.

to confirm use your mouse scroll button to zoom in and out of two fullscreen viewports...

Instead what you want to do for testing is move your mouse to a 3DView of the other window and press "G". In older versions of Blender you would need to first click the window to activate it. With this new "auto activate" behavior the window should automatically become active and work without having to click it.

> @funty - Unless I am missing something here...see a shade change when you mouse over. What you are seeing is the other window respond to _mouse_ movement and input, but what would not work is **keyboard** entry and shortcuts. On Windows, keyboard events are only sent to the (one) active window, which you can see gets a different title bar color. > to confirm use your mouse scroll button to zoom in and out of two fullscreen viewports... Instead what you want to do for testing is move your mouse to a 3DView of the other window and press "G". In older versions of Blender you would need to first click the window to activate it. With this new "auto activate" behavior the window _should_ automatically become active and work without having to click it.

👍 1

funty commented

2023-07-10 18:12:17 +02:00

@Harley

Yes I see it does not respond with keyboard input when both windows are fullscreen. Otherwise it does.

@Harley Yes I see it does not respond with keyboard input when both windows are fullscreen. Otherwise it does.

❤️ 1

funty commented

2023-07-10 19:46:06 +02:00

@Harley

After further experimentation, for some reason, its working as you said it should be. I tried the following, with both windows at fullscreen:

G, R, S
Number pad +, and - to zoom in and out
CTRL + A for the popup
A to select all

I have no idea what I did differently from the last time I checked it, before I replied, other than close Blender and restart it.

And I am still confused, as to what the issue is.

@Harley After further experimentation, for some reason, its working as you said it should be. I tried the following, with both windows at fullscreen: - G, R, S - Number pad +, and - to zoom in and out - CTRL + A for the popup - A to select all I have no idea what I did differently from the last time I checked it, before I replied, other than close Blender and restart it. And I am still confused, as to what the issue is.

funty commented

2023-07-10 19:57:42 +02:00

@Harley

Alright, I believe I may have narrowed it down. Hopefully, this will help clear things out.

When I select Window > New Window, everything works as it should, keyboard input responds as it should with fullscreen windows.

However, when I select Window > New Main Window, that is when the OP issue arises. Keyboard input no longer works as it does with Window > New Window, when you have fullscreen windows open.

@Harley Alright, I believe I may have narrowed it down. Hopefully, this will help clear things out. When I select Window > New Window, everything works as it should, keyboard input responds as it should with fullscreen windows. However, when I select Window > New Main Window, that is when the OP issue arises. Keyboard input no longer works as it does with Window > New Window, when you have fullscreen windows open.

Harley Acheson commented

2023-07-10 22:09:25 +02:00

We can't auto-activat ALL windows, as there are some times when that is annoying. So we do so in these circumstances:

Parent to its child
Child to its parent
between siblings (same parent)
between main windows that don't overlap.

In this case we have two main windows. This works as I expect unless BOTH windows are maximized on adjacent monitors. Unfortunately the Windows API call GetWindowRect retrieves a rectangle that includes the window's dropshadow, which means that they are detected as overlapping if they share an edge.

So this error does not require multiple monitors or the maximization of the windows. Simply make the main Blender window less than half the width of a monitor. Select Window / New Window and arrange the two windows so that they are next to each other. If they are closer than about 20 pixels they won't auto-activate.

Will have to think of a nice way to fix this. Might have to use DwmGetWindowAttribute with DWMWA_EXTENDED_FRAME_BOUNDS, but I think that is not adjusted for DPI.

We can't auto-activat ALL windows, as there are some times when that is annoying. So we do so in these circumstances: * Parent to its child * Child to its parent * between siblings (same parent) * **between main windows that don't overlap**. In this case we have two main windows. This works as I expect unless BOTH windows are maximized on adjacent monitors. Unfortunately the Windows API call `GetWindowRect` retrieves a rectangle that includes the window's dropshadow, which means that they are detected as overlapping if they share an edge. So this error does not require multiple monitors or the maximization of the windows. Simply make the main Blender window less than half the width of a monitor. Select Window / New Window and arrange the two windows so that they are next to each other. If they are closer than about 20 pixels they won't auto-activate. Will have to think of a nice way to fix this. Might have to use DwmGetWindowAttribute with DWMWA_EXTENDED_FRAME_BOUNDS, but I think that is not adjusted for DPI.

Harley Acheson referenced a pull request that will close this issue

2023-07-11 01:18:13 +02:00

Fix #109886: Win32 AutoFocus Between Main Windows #109946

Harley Acheson referenced this issue from a commit

2023-07-11 21:13:58 +02:00

Fix #109886: Win32 AutoFocus Between Main Windows

Harley Acheson closed this issue

2023-07-11 21:14:00 +02:00

Blender Bot added

Status

Resolved

and removed