max / audiofiles

Describe the Add Library form's fields Takes makeover-layout 0.8.2 and makeover-immediate 0.5.2, and puts the first two audiofiles call sites onto the description. The name input becomes a Field: a well, a label, a required marker, and an error line. The error is new behaviour and closes a hole -- with a folder chosen and no name, "Create New" disabled itself and said nothing about why. The storage style becomes a FieldKind::Radio, the kind added upstream for this call site. The comment above it already said why the choice must not sit behind a closed control (copying samples in or referencing them in place cannot be changed later); the description can say that now instead of the app enforcing it by hand. The one fact that applies to the whole question moves into the field's hint, where it is visible rather than hover-only. The folder picker stays hand-rolled. A path-picker kind would be decoration in both renderers -- the value is a string either way and the dialog is the app's job -- and this vocabulary's bar is that a kind changes what a renderer does. theme.rs: extreme_bg_color was the page and is now the well. egui fills what you look into with it, text edits above all, so a described field and all 21 widgets::text_field sites were painting two different shades of well. It was the last place still substituting the page for a well token, which makeover 2.3.0 derived and palette() already documents having outgrown. widgets::field wraps the renderer with this app's palette and geometry, the way raised_frame and inset_well already do. Bare checkboxes deliberately stay as ui.checkbox: under field() one is ui.checkbox plus a required marker at three times the source. A described field asks a labelled question with help, validation, options or a well; a bare toggle is a control. dialog.rs: fold a match into ?, which clippy had been flagging.