e7af54898e
Unfortunately there is no way to get this information from Qt, so I had to resort to some funny low-level C-like Python programming to directly use libwayland-client and Xlib. Fun was had! Hopefully this avoids having to ask for this information every time someone shows a bug/crash report, as there are various subtleties that can be specific to the Wayland compositor in use. |
||
|---|---|---|
| .. | ||
| usertypes | ||
| overflow_test_cases.py | ||
| test_debug.py | ||
| test_error.py | ||
| test_javascript.py | ||
| test_jinja.py | ||
| test_log.py | ||
| test_qtlog.py | ||
| test_qtutils.py | ||
| test_resources.py | ||
| test_standarddir.py | ||
| test_urlmatch.py | ||
| test_urlutils.py | ||
| test_utils.py | ||
| test_version.py | ||