Wayland: Unable to access window position, finding the window under the cursor doesn't work #98928
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#98928
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
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.
SCREEN_OT_area_swap
isn't able to swap areas with another window.datadropper_win_area_find
wont be able to access other windows.wm_event_cursor_other_windows
).Currently
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
Added subscriber: @ideasman42
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:
xdg_popup_listener.configure
.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.
Wayland unable to access window position, finding the window under the cursor doesn't workto Wayland: Unable to access window position, finding the window under the cursor doesn't work@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).