Do not treat structs with one value as simple values in the "Simulation Data" tab.
Arrays of structs were considered too complex and forced into
"JSON mode". That is not necessary, so do not do that.
Closes: #9889
* Iintialize tristate
* Control the check_box.check_state always using the set_check_state function
Reason: Otherwise the tristate is not handled properly
* Handle tristate directly in checkbox
* fix documentation
Copy board-specific memory.x to OUT_DIR and add it to the linker search path. This ensures the STM32H735G board-specific memory.x takes precedence over any generic memory.x from dependencies like ft5336.
Fixes: #10035
I kept seeing distracting warnings when working with these testcases,
and it's better to have good examples when writing new testcases.
I didn't touch the issue_*.slint regression tests, so those will
still be testing the old syntax.
Rename grid to grid_simple, otherwise
cargo test -p test-driver-interpreter -- test_interpreter_layout_grid
runs multiple tests, no way to run only that one.
Same for nested_grid.slint given that there's a nested_grid_2.slint
* Change Color type to be f32 internally but no other changes
* Add missing clamp
* Add round function as we're not on MSRV 1.90+
* Prepare for being able to switch between u8s and f32s
* [autofix.ci] apply automated fixes
* Fix Display impl
* Add feature flag for 8-bit color values. Name to be bikeshed
* Fix brighter-darker test
* Update test screenshot
* Remove unused Float trait import
* Add cfg thing for not(cbindgen)
* Change Channel to float in cbindgen
* Change the cpp color type for uint8_t for now
* Opt cpp into 8-bit-color
* Switch feature around
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
For macOS and Windows we've had hard-coded fallbacks, but none for Linux
after the fontconfig removal. So go through the same fallback families
as when using fontique regularly, and add emoji as parley tries that
within.
This fixes picking up glyphs such as "←→↵⌫".
Fixes#9866
The material style defines a `StyleMetrics.default-font-family` which is
meant to be applied to `Window` element if not set by the user.
But it was mistakely sometimes applied to PopupWindow
Consider this code:
```slint
component MyPopup inherits PopupWindow {
Text { text: "Hello"; }
}
export component MainWindow inherits Window {
my_popup := MyPopup { }
}
```
First, we would process MyPopup: `apply_default_property_from_style`
wouldn't do anything, but the `lower_popups` pass would replace its
root with a Window builtin.
Second, we would process MainWindow: `apply_default_property_from_style`
would see that my_popup is using the Window as a builtin and would apply
default window properties from style, which it shouldn't.
In fact, `apply_default_property_from_style` should only apply default
for elements that are directly using the builtin, not a component that
inherits from that builtin, as these property should have been already
set.
Biome was raising this error:
> A "floating" Promise was found, meaning it is not properly handled and
> could lead to ignored errors or unexpected behavior.
Biome is of course right, so handle errors by logging them.
* ModalNavigationDrawer: add possibility to react on selection changes of group and item simultaneously like in NavigationDrawer
* Add arguments and their description to the documentation
* align style
50GB of caches in branches is still being created. This doesn't
eliminate them all but makes a decent dent. This stops the more useful
master branch cache being evicted.
* Use htmlparser
* Parse color values
* Cargo fmt
* Use imported Color
* Actually handle colors via overrides
* Check that the tags match
* Use color parsing feature
* Make htmlparser optional
* Error handling
* [autofix.ci] apply automated fixes
* debug_log!
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
