Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston
David Edmundson
david at davidedmundson.co.uk
Fri Feb 23 08:35:36 UTC 2024
On Fri, Feb 23, 2024 at 6:15 AM Terry Barnaby <terry1 at beam.ltd.uk> wrote:
>I don't know how to determine the Wayland surface ID from a
> wl_surface pointer unfortunately to really check this.
wl_proxy_get_id(static_cast<wl_proxy*>(myWlSurface));
> >> Possibly when QWidget is below in hierarcy to be a child of of a parent,
> >> as described in
That's fine.
A QWidget with WA_NativeWindow will create a QWindow with a parent. A
QWindow with a parent will create a subsurface in wayland terms.
But it is a subsurface where Qt is managing it and you're also
committing on it, which can be a bit confusing and going through
widgets to create a subsurface isn't really needed.
There's a bunch of other options there.
---
Can you link your test app. You can send me a private email and I'll
take a look. It doesn't seem like a core wayland problem more a
Qt/application setup issue so far. Then we can follow it up on Qt's
Jira if there is a Qt issue.
David Edmundson - QtWayland Maintainer
More information about the wayland-devel
mailing list