Olivier Goffart

> replace "popup" for combo boxes with a wider/bigger dedicated "dialog" that is touch friendly (centered on the screen) That's the only part missing

closing this as the printerdemo_mcu is just what we use.

See #1280

@DemiMarie : Thanks for your comment. We have actually started to work to improve our support for accessibility, and are actually working in an `accessibility` branch (#1193 and #1194). But...

Yes, We want to do a tree view somehow The cargo-ui repository already have a straw man implementation, but it need to be polished and generalized. https://github.com/slint-ui/cargo-ui/blob/91bee62fbedad92b3fad4fc04d30c2ebb5d477ad/ui/cargo.slint#L179-L193

I think we need to reconsider something regarding unqualified lookup: we want that adding properties to elements is not a breaking change. Same for enum values or types. Also a...

Having a design tool has been one goal since before we began to code. But as LoganDark said, we first needed a somehow working library before doing it. We also...

The qt_viewer reparent the QWidget to anothe QWidget window which is on the stack. and closing the qt_viewer dostroy that widget (and hence the slint QWidget (`SlintWidget`) before the window...

So the crash is worked around in the qt_viewer by commit [590ef33](https://github.com/slint-ui/slint/commit/590ef33018415ad975daa100c4f5367508ffe471) The question is: is that something we should support? (destroying deleting QWidget* before destroying the Slint handle?)

I have been thinking allowing two way binding with converstion. As long as the compiler can invert the expression. For example ``` foo bar + 1; // can be inverted...