Simon Hausmann

Olivier was kind enough to implement keyboard support today ❤️ https://github.com/slint-ui/slint/pull/3197

We're trying to sort out how to model the RWH api with the interior mutability of the winit window owner. Meanwhile https://github.com/slint-ui/slint/pull/2617 adds API to the i-slint-backend-winit crate to provide...

For Qt, commit db9b6a5cf6f664bfdd4ca4cfc8207266e89392f2 in the Slint repo attempts to implement RHW support for the Qt backend. This works on macOS and Windows, but requires the use of private API....

Beyond #2865 I'm going to file a few tickets under the [accessibility label](https://github.com/slint-ui/slint/labels/accessibility), so that we can track further improvements. My objective is to close this task when #2865 lands...

I can't reproduce this :(. The slide_puzzle example works well for me with Qt and it is showing the "Plaster" font as expected. @lukas-jung, do you happen to remember how...

> In particular, this will force the evaluation of the property at component creation no matter if the propery is queried by other mean (even if the component is hidden)....

I thought about this more and I've come to the conclusion that - unless this virtual-webgl solution easily plugs in - we should switch to entirely CPU based rendering for...

It's not so much of a problem for _us_ in the docs, but the problem still exists and it is valid AFAICS. Our wasm builds do rendering using GPU resources...

This is fixed when using the Skia renderer, but keeping this open for the text/glyph handling around femtovg.

Great that you managed to get that far with Swift bindings - thanks for sharing!