Simon Hausmann

Ah yes, you're right. I'm leaning towards (1). You?

We discussed this a bit and came up with a possible plan: 1. A shadow applied to a `for`-repeated element would generate a second `for`, which mirrors the original `for`...

Hi Martin! Hah, I was just building Slint with Yocto for the imx8 board we have from you (using fsimx8mp-Y2023.09). You're targeting a Linux system, so you should not need...

Tagging this as needs-info as it's unclear what the desired use of SLINT_FEATURE_FREESTANDING=ON is in a Linux target environment - perhaps we should throw an error if that's configured?

"Should this include the qt style?" is one of the option questions...

> These tests are needed. > > You took a different approach than i would have done. I would have kept the driverlib as is, and made the detection of...

> (which i would have called "widgets") I thought about this again, and you're right. We already have `widgets` and then it makes sense that every .slint test file that...

So this is one of those differences... The "other" styles have a TextEdit inside a SpinBox, which responds to the enter key. The Qt spinbox doesn't have that, but it...

My guts feeling is that the SpinBox should not be editable by default, but that should be controllable via an "editable" boolean property. I'm not sure this can be supported...

> All theses palettes should be accessible through the std-widgets.slint import. Does that mean that regardless of the currently selected style, I can always `import { CupertinoPalette } from "std-widgets.slint"`...