238dd2a8ea
In the recent changes for handling map/unmap events on Wayland's wxGLCanvasEGL, we use the following GTK widget signals: * The "map-event" signal to create the canvas's subsurface. The earlier "map" signal can not be used, as the associated toplevel window's Wayland surface may not yet exist by the time we receive it. * The "unmap" signal to destroy the canvas's subsurface. Using the later "unmap-event" signal is problematic, due to other resources we build upon being already destroyed by then. Usually, the "map-event" signal comes before "unmap" and resources are created and destroyed appropriately. However, there's an edge case: If a canvas is shown and then immediately hidden (before wxWidgets can pump from the event loop), "unmap" will come before "map-event". This happens because signals like "map" and "unmap" are delivered immediately (when calling e.g. `gtk_widget_hide`), while signals like "map-event" and "unmap-event" are delivered later on the event loop. For the same reason, showing a canvas, then immediately hiding it, then immediately showing it again, will cause two "map-event"s to get delivered enqueued without a "unmap" in between. This condition can be hit quite easily when setting up a complex UIs, and in particular it is triggered by Aegisub during startup, leading to a crash (Wayland protocol error) when opening a video later, or when specifying a video directly on the startup command line. To avoid this breaking our resource management, add some checks to detect those "map-event"s we shouldn't handle - either the ones that happen after "unmap", or the duplicate ones without an "unmap" in between. See #23961, #23968. (cherry picked from commit 133f7731b25df46bd99519e7c52cf4a90ca2cc1a) |
||
|---|---|---|
| .circleci | ||
| .github | ||
| 3rdparty | ||
| art | ||
| build | ||
| demos | ||
| distrib | ||
| docs | ||
| include | ||
| interface | ||
| lib | ||
| locale | ||
| misc | ||
| samples | ||
| src | ||
| tests | ||
| utils | ||
| .cirrus.yml | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| acinclude.m4 | ||
| aclocal.m4 | ||
| appveyor.yml | ||
| autoconf_inc.m4 | ||
| autogen.sh | ||
| CMakeLists.txt | ||
| config.guess | ||
| config.sub | ||
| configure | ||
| configure.in | ||
| descrip.mms | ||
| install-sh | ||
| Makefile.in | ||
| mkinstalldirs | ||
| README-GIT.md | ||
| README.md | ||
| regen | ||
| setup.h_vms | ||
| setup.h.in | ||
| version-script.in | ||
| wx-config-inplace.in | ||
| wx-config.in | ||
| wxwidgets.props | ||
| wxwin.m4 | ||
About
wxWidgets is a free and open source cross-platform C++ framework for writing advanced GUI applications using native controls.
wxWidgets allows you to write native-looking GUI applications for all the major desktop platforms and also helps with abstracting the differences in the non-GUI aspects between them. It is free for the use in both open source and commercial applications, comes with the full, easy to read and modify, source and extensive documentation and a collection of more than a hundred examples. You can learn more about wxWidgets at https://www.wxwidgets.org/ and read its documentation online at https://docs.wxwidgets.org/
Platforms
This version of wxWidgets supports the following primary platforms:
- Windows XP, Vista, 7, 8, 10 and 11 (32/64 bits).
- Most Unix variants using the GTK+ toolkit (version 2.6 or newer or 3.x).
- macOS (10.10 or newer) using Cocoa under both amd64 and ARM platforms.
Most popular C++ compilers are supported including but not limited to:
- Microsoft Visual C++ 2005 or later (up to 2022).
- g++ 4 or later (up to 12), including MinGW/MinGW-64/TDM under Windows.
- Clang (up to 14).
- Intel icc compiler.
- Oracle (ex-Sun) CC.
Licence
wxWidgets licence is a modified version of LGPL explicitly allowing not distributing the sources of an application using the library even in the case of static linking.
Building
For building the library, please see platform-specific documentation under
docs/<port> directory, e.g. here are the instructions for
wxGTK, wxMSW and
wxOSX.
If you're building the sources checked out from Git, and not from a released version, please see these additional Git-specific notes.
Further information
If you are looking for community support, you can get it from
- Mailing Lists
- Discussion Forums
- #wxwidgets IRC channel
- Stack Overflow
(tag your questions with
wxwidgets) - And you can report bugs at GitHub
Commercial support is also available.
Finally, keep in mind that wxWidgets is an open source project collaboratively developed by its users and your contributions to it are always welcome. Please check our guidelines if you'd like to do it.
Have fun!
The wxWidgets Team.