On Wed, 21 Feb 2024 11:08:02 -0500
jleivent wrote:
> Not completely blocking makes sense for the compositor, but why not
> block the client?
Blocking in clients is indeed less of a problem, but:
- Clients do not usually have requests they *have to* send to the
compositor even if the composito
Thanks for this response. I am considering adding unbounded buffering
to my Wayland middleware project, and wanted to consider the flow
control options first. Walking through the reasonsing here is very
helpful. I didn't know that there was a built-in expectation that
clients would do some of th
Hi,
We are developing a video processing system that runs on an NXP imx8
processor using a Yocto embedded Linux system that has Qt6, GStreamer,
Wayland and Weston.
We are having a problem displaying the video stream from GStreamer on a
QWidget. In the past we had this working with Qt5 and ol
Hi,
On Thu, Feb 22, 2024 at 03:21:01PM +, Terry Barnaby wrote:
> Hi,
>
> We are developing a video processing system that runs on an NXP imx8
> processor using a Yocto embedded Linux system that has Qt6, GStreamer,
> Wayland and Weston.
>
> We are having a problem displaying the video stream
Hi Marius,
Many thanks for the info.
Some notes/questions below:
Terry
On 22/02/2024 17:49, Marius Vlad wrote:
Hi,
On Thu, Feb 22, 2024 at 03:21:01PM +, Terry Barnaby wrote:
Hi,
We are developing a video processing system that runs on an NXP imx8
processor using a Yocto embedded Linux sy
I have tried using "weston-debug scene-graph" and I am coming to the
conclusion that qtwayland 6.5.0 is not really using native Wayland
surfaces when Qt::WA_NativeWindow is used. From what I can see (and I
could easily be wrong) the Wayland protocol shows wl_surfaces being
created and two QWidg
