Split area feature messed up then other window in background. #129414

New Issue

MultLabs · 2024-10-26T17:38:30+02:00

MultLabs commented

2024-10-26 17:38:30 +02:00

System Information
Operating system: Linux-6.5.0-14-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.146.02

Blender Version
Broken: version: 4.3.0 Beta, branch: blender-v4.3-release, commit date: 2024-10-25 18:17, hash: 1dd6cdb1727f
Worked: 4.2

Short description of error
Split area feature messed up then other window in background. You try to split the area by dragging the corner, instead the area goes in window at background. Look at the video:

Exact steps for others to reproduce the error
I can't say that it happened in 100% cases.

**System Information** Operating system: Linux-6.5.0-14-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.146.02 **Blender Version** Broken: version: 4.3.0 Beta, branch: blender-v4.3-release, commit date: 2024-10-25 18:17, hash: `1dd6cdb1727f` Worked: 4.2 **Short description of error** Split area feature messed up then other window in background. You try to split the area by dragging the corner, instead the area goes in window at background. Look at the video: <video src="/attachments/5451c821-23b5-4340-8226-6ef9642b1c56" title="2024-10-26_18-32-52.mp4" controls></video> **Exact steps for others to reproduce the error** I can't say that it happened in 100% cases.

2024-10-26_18-32-52.mp4

3.9 MiB

MultLabs added the

labels 2024-10-26 17:38:31 +02:00

Alaska commented

2024-10-27 09:09:26 +01:00

I can confirm the issue here on Linux (Gnome X11), but couldn't on Windows or macOS.

CC @Harley as the developer of the feature, and CC @ideasman42 due to their involvment in Linux windowing development.

System Information
Operating system: Linux-6.8.0-41-generic-x86_64-with-glibc2.39 64 Bits, X11 UI
Graphics card: Mesa Intel(R) Arc(tm) A750 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 24.0.9-0ubuntu0.1
Blender version: 4.3.0 Beta, branch: blender-v4.3-release, commit date: 2024-10-25 18:17, hash: 1dd6cdb1727f

I can confirm the issue here on Linux (Gnome X11), but couldn't on Windows or macOS. CC @Harley as the developer of the feature, and CC @ideasman42 due to their involvment in Linux windowing development. **System Information** Operating system: Linux-6.8.0-41-generic-x86_64-with-glibc2.39 64 Bits, X11 UI Graphics card: Mesa Intel(R) Arc(tm) A750 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 24.0.9-0ubuntu0.1 Blender version: 4.3.0 Beta, branch: blender-v4.3-release, commit date: 2024-10-25 18:17, hash: `1dd6cdb1727f`

Alaska added

and removed

labels 2024-10-27 09:09:47 +01:00

Harley Acheson commented

2024-11-01 15:10:31 +01:00

The video and description doesn’t detail how these multiple windows were created and in what order. And I think that is significant here. Sorry that I am away from my computer so the following is guesses from memory.

When doing operations between multiple windows it is necessary to know what window is the topmost one at the mouse position. Relative z-depth of the windows is not something we directly track, so in order for this to work flawlessly we need to ask the operating system. I don’t believe we do this for X11 so there can be times when this is incorrect.

The base behaviour, when there isn’t platform-specific code, for “what is the topmost window at this position” is to test the position against all our windows, and - when multiples- assume windows created later are on top of those created earlier, as that is more likely.

For Windows, (I think) MacOS, and (probably) Wayland, we instead call OS-supplied functions, specific to this purpose, and so always get the correct answer. Unless we get X11-specific code for this it will be possible to get bad behaviour for area interactions, drag and drop, etc if a window is above another that was created after it.

The video and description doesn’t detail how these multiple windows were created and in what order. And I think that is significant here. Sorry that I am away from my computer so the following is guesses from memory. When doing operations between multiple windows it is necessary to know what window is the **topmost** one at the mouse position. Relative z-depth of the windows is not something we directly track, so in order for this to work flawlessly we need to ask the operating system. I don’t believe we do this for X11 so there can be times when this is incorrect. The base behaviour, when there isn’t platform-specific code, for “what is the topmost window at this position” is to test the position against all our windows, and - when multiples- assume windows created later are on top of those created earlier, as that is more likely. For Windows, (I think) MacOS, and (probably) Wayland, we instead call OS-supplied functions, specific to this purpose, and so always get the correct answer. Unless we get X11-specific code for this it will be possible to get bad behaviour for area interactions, drag and drop, etc if a window is above another that was created after it.

Alaska commented

2024-11-02 00:57:03 +01:00

The video and description doesn’t detail how these multiple windows were created and in what order. And I think that is significant here.

When I ran my tests, I started with a small window, then created a new window and placed it behind the existing window.

The base behaviour, when there isn’t platform-specific code, for “what is the topmost window at this position” is to test the position against all our windows, and - when multiples- assume windows created later are on top of those created earlier, as that is more likely.

Based on my testing here, this does seem to be what's happening. Windows created later are given priority.

> The video and description doesn’t detail how these multiple windows were created and in what order. And I think that is significant here. When I ran my tests, I started with a small window, then created a new window and placed it behind the existing window. > The base behaviour, when there isn’t platform-specific code, for “what is the topmost window at this position” is to test the position against all our windows, and - when multiples- assume windows created later are on top of those created earlier, as that is more likely. Based on my testing here, this does seem to be what's happening. Windows created later are given priority.

MultLabs commented

2024-11-02 07:11:54 +01:00

The video and description doesn’t detail how these multiple windows were created and in what order.

I made this two-window setup for two monitors in Blender 2.80, and haven't been changed it since that time. But it looks like the main window in the foreground creates first.

> The video and description doesn’t detail how these multiple windows were created and in what order. I made this two-window setup for two monitors in Blender 2.80, and haven't been changed it since that time. But it looks like the main window in the foreground creates first.

Julian Eisel added this to the 4.3 milestone 2024-11-05 18:38:47 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Split area feature messed up then other window in background. #129414