Olivier Goffart

> Is there some suggested workaround for now? It depends a bit of what you're doing. But we can use a workaround similar to the missing changed event https://github.com/slint-ui/slint/issues/112#issuecomment-1065866865 ```rust...

We just would need to find a good syntax for it. ```rust // Like in rust for xx in model.filter(|x| x.tag == root.tag) : Rectangle { // like in JS...

If you change the return value of a function, it is a breaking change. ```rust fn remove(model: &mut VecModel) { model.remove(42) // note: no semi colon } ```

Maybe we actually don't want this API like that and want to have it only for `Dialog` or something perhaps this could be a callback instead.

I think there should be only one page for MCU and not two. The explanation on how to run the demo should also be in the docs. And maybe a...

> I was actually planning to move the demo stuff over to the README of the printerdemo_mcu. That is where I would look for that information. Yes, that's fine too...

Looks like an issue that is caused by Qt not being found. Do you see a warning earlier in the compilation about Qt not being build? (Regardless, i think it...

I just learned today that warning that we show in our build.rs script are actually not printed in the console because cargo don't print warning for dependencies from crates.io :-(

I think this is basically what Global objects are: https://slint-ui.com/releases/0.3.1/docs/cpp/markdown/recipes/recipes.html#global-callbacks

Why not keep the state in the LineRenderer itself? (yeah, this will be useless when using the rendering by buffer, but it's not so much data) Also this is only...