Simon Hausmann

> I don't think that's the right way to do it. > We should not disable the other backend. Is there a benefit to shipping unused backend/rendering code in the...

> > Okay, if everything means literally everything then we can't do this change, as we can't select Skia for the wasm build and thus can't make it the default....

> > We can have different default feature for different architecture though. > > How is this possible? > > in the backend-selector > > ```toml > [target.'cfg(not(target_arch = "wasm32"))'.dependencies]...

Ok, agreed, this should be done in line with changing the default renderer for winit when Qt is not available. Separate PR.

Hi! I think @Montel had a somewhat similar issue in #1200 . Odd though that the the workaround that helped there and that you also tried (setting `QT_INCLUDE_PATH` and `QT_LIBRARY_PATH`)...

I think similar to `renderer-winit-skia-opengl` this would be a crate feature to enable the compile-time support for it and when Skia is selected, that would be the method of rendering.

Yeah unfortunately we don’t respond to IME events and queries right now, apart from Oliver’s recent fix for IME commits. Both winit and Qt have APIs that should make it...

This is fixed by https://github.com/slint-ui/slint/pull/1728

That’s a little unusual. You’re on Linux, right? Are you using Wayland or X11?

I think it’s a good idea to add support for this. Implementation wise I think yon might need some platform cfg guards. Which platforms support this or how this maps...