Simon Hausmann

> we need to specify it before creating the window. So before we actually have a slint::Window. So that might not be possible? Right, we need to know the id...

> then perhaps a global function should be use like slint::set_app_id or set_xdg_id or something like that. Ah, you're right - this isn't per window anyway. In Qt it's also...

I still maintain that this is best handled as a global property. The common case is that one process has one or multiple windows that belong to the same application...

I think that is only a consequence of the use of a path stroke - as you suspect. If you change the stroke width to zero the paths align. The...

Yes, I agree. We have other similar issues with the path rendering also in the iot dashboard with femtovg. I've been contemplating trying to replace the custom stroker and tesselator...

I agree, an imperative painter API is rather tempting. The main downside I see is that it makes it harder to map to declarative "output" such as the DOM, and...

We discussed this further a bit today and one way to address the laziness would be to treat each handler as if it were tracking a "gui" related property. So...

Hey. That’s awesome :). I’m a bit unsure about mdbook for reference documentation, but that doesn’t mean it can’t work. One motivation is the ability to search well through the...

> Note that the Qt native style renders the widgets with the default QWidget font, so the font size has no effect for them. Ah yes, we have a dummy...

I can reproduce this (with fluent style). It seems `TouchArea` needs a `wheel-event` callback.