Wayland: Unable to access window position, finding the window under the cursor doesn't work #98928
Wayland can't access window positions. From what I can tell this is an intentional limitation and there aren't ways to access this information.
This means functions such as
WM_window_find_under_cursor doesn't work.
From the user perspective the following functionality wont work.
- "Swap Areas" /
SCREEN_OT_area_swapisn't able to swap areas with another window.
- Some "Eyedropper" functions such as
datadropper_win_area_findwont be able to access other windows.
- Dragging items between windows doesn't work (see
GHOST_SupportsWindowPosition() has been added to prevent other windows being found when they shouldn't be.
NOTE: there is a proposed solution that might allow Blender to restore the positions of windows saved in a file: see: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/18
Note that while it's not possible to access the absolute window locations, a way to workaround this could be to define one window being the parent of all other windows, in that case it's possible to find the window location relative to the parent window, although this requires the child windows to be popups. See:
In the case of dragging items, we could look into supporting OS-level drag & drop, instead of bypassing the windowing system in the case of Blender dragging into other Blender windows.
@ideasman42 hi, this report is now displayed under "Untriaged reports list" (after Gitea migration).
From report description, this seems a known issue/limitation for Wayland, can you confirm it in that case?
Or is this fixed already? :)
@PratikPB2123 it's a known issue, I opened it to keep track of any problems related to the inability to know absolute positions of windows.
(set as known-issue).
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?