mirror of
https://github.com/rmcrackan/Libation.git
synced 2026-09-20 11:32:25 -04:00
Allamagoosa
381cf307f7
Bounding the persisted setting by processor count was only half of it. Both spinners take their maximum from the same machine-derived number and are two-way, so a NumericUpDown handed a value above its maximum coerces the display down and writes the coerced value straight back. A user who chose 8 on their desktop and opened the queue panel on a two-core laptop still ended up with 8 replaced by 2 - the same defect, one layer up, and not fixed by the configuration change alone. The bound is now the machine's capability or the stored value, whichever is higher, so the spinner can never coerce what is already there. Lowering it remains the user's to do, and what actually runs is still held down to what the machine can manage at the point of use.