i509VCB

class names seem fine otherwise. would like the nicer package though.

Essentially I need to inherit access wideners from another subproject by applying both the access widener from the main and subproject. I do think it would require adding an array...

I personally don't see a real purpose for the additions here. Yes it may make things more convenient but this just adds duplicate registration logic where the (Fabric)MaterialBuilder or overriding...

We can actually get this show on the road since networking-v1 has been merged.

cc @PolyMeilex

In the alacritty issue, I assume by qxdisplay you are referring to this: https://github.com/sailfish-containers/qxdisplay

Could you run `wayland-info` inside the container and report the output? Based on the alacritty issue I think might be an issue with qxdisplay, that command should reveal some more...

Well that does show the environment is set, which is expected because alacritty did not fail to create the event loop. The output of `wayland-info` would help a lot since...

Looking at the qt compositor reference, you might have to take things into your own hands: https://doc.qt.io/qt-5/qtwayland-compositor-qmlmodule.html There isn't any `WaylandSubcompositor` type I can easily find but I think some...

I'll integrate the changes from #531 when that is merged