behaviour-tree-test/platform
Riteo a3913b045d Wayland: Fix stuck pointer buttons on window leave
This issue came from the frame-based refactoring done in the multiwin
PR.

It looks like some (all?) compositors group certain events alongside
`wl_pointer::leave`, which I absolutely did not expect. The docs don't
seem to mention it either from what I can tell.

We now fall-back on the old pointed window if and only if the current
window is invalid and the old one isn't. Each state fetch is guarded
with an `ERR_FAIL_NULL` so this should still catch any potentially
corrupted window with missing data but a valid ID.

I also added the usual big comment so that this "quirk" does not get
lost to time.
2025-05-14 23:30:16 +02:00
..
android Bump the minimum supported SDK version to 24 2025-05-08 09:45:32 -04:00
ios Fix empty lines being added for errors with no script backtrace 2025-05-05 13:27:21 +02:00
linuxbsd Wayland: Fix stuck pointer buttons on window leave 2025-05-14 23:30:16 +02:00
macos Merge pull request #106139 from akien-mga/crash-handler-backtrace-print 2025-05-07 12:48:25 -05:00
web Core: Modernize C headers with C++ equivalents 2025-05-02 08:23:01 -05:00
windows Improve script backtrace print in crash handlers 2025-05-07 09:52:50 +02:00
platform_builders.py SCons: Begin decoupling generation & build code 2025-04-25 08:23:01 -05:00
register_platform_apis.h Style: Replace header guards with #pragma once 2025-03-07 17:33:47 -06:00
SCsub SCons: Begin decoupling generation & build code 2025-04-25 08:23:01 -05:00