mirror of
https://github.com/rmcrackan/Libation.git
synced 2026-09-12 21:57:19 -04:00
Allamagoosa
1eddccbe63
Taking the alternative offered in review. The spinner's maximum is the flat hard limit now, the same number in both UIs and on every machine, and machine capability is applied only at the point of use. Bounding the control by capability made it lie in two directions at once. Below the stored value, a two-way spinner coerces its display down to its maximum and writes that back, so opening the panel on a smaller machine overwrote an 8 chosen on a larger one. Raising the bound to meet the stored value fixed that but left a stored 8 displaying 8 on a two-core box that will only ever run 2. The two UIs had also drifted apart: Avalonia bound Maximum and ratcheted down, WinForms set it once in the constructor, so within a session you could lower and re-raise in one and not the other. What is left is the gap between what the setting says and what runs, and that is now stated rather than hidden. Chardonnay shows "(2 on this machine)" beside the spinner, in the spare column the settings row already had. Classic's settings table is full at three columns with no width to spare, so it says the same thing in the control's tooltip.