Thanks for the clear reproduction. I was able to reproduce this and it’s now fixed in the next release: https://feedback.objo.dev/bug/670
The underlying issue was that Slider is backed by Avalonia’s range control, which requires:
Minimum <= Value <= Maximum
Studio could save a layout with Value = 100, Minimum = 102, and the default Maximum = 100. When the app ran, those values were applied separately and Avalonia threw an unhandled exception.
The fix is now in place:
Slider and ProgressBar now coerce range values safely at runtime.
- Studio normalises invalid range values when loading/deserialising layouts.
- The inspector now updates
Value, Minimum, and Maximum together after a range edit, so it won’t display an inconsistent state.
So if you set Minimum above the current Value/Maximum, Studio will bring the range back into a valid state rather than letting the app crash.