Skip to main content

max / makeover-immediate

0.8.0: take makeover-layout 0.11, and where a file field lands
Author: Max Johnson <me@maxj.phd> · 2026-08-09 15:48 UTC
Signed with PGP, not checked
Commit: 38a4cf2fa130d19e3d6ff3d4514cea55b4aaae67
Parent: 8c28410
2 files changed, +11 insertions, -2 deletions
M Cargo.toml +2 -2
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "makeover-immediate"
3 - version = "0.7.0"
3 + version = "0.8.0"
4 4 edition = "2024"
5 5 description = "The immediate-mode renderer for makeover-layout. Immediate mode is the constraint that matters, not the library: no cascade, no retained tree, one stroke per widget. Backed by egui."
6 6 license = "MIT"
@@ -8,7 +8,7 @@
8 8
9 9 [dependencies]
10 10 egui = { version = "0.35", default-features = false }
11 - makeover-layout = "0.10"
11 + makeover-layout = "0.11"
12 12
13 13 [lints.rust]
14 14 unused = "warn"
M src/lib.rs +9
@@ -361,6 +361,15 @@
361 361 /// The wildcard falls to [`Control::Typed`] on purpose: a kind added to the
362 362 /// description since this renderer was built degrades to a text box, which
363 363 /// accepts any value the others would, rather than to nothing drawn at all.
364 + ///
365 + /// `FieldKind::File` lands there as of makeover-layout 0.11.0, and it is left
366 + /// there rather than grown a shape of its own. egui's honest answer is a button
367 + /// that opens a native picker, which is a fifth control and a file-dialog
368 + /// dependency; no consumer of this crate asks for a file field yet. Same
369 + /// position this crate took on `Meter` at 0.10.0: the membership test is that
370 + /// every renderer *could* answer honestly, not that each one does on the day.
371 + /// A path in a text box is not nothing, and it is what an app that needs this
372 + /// tomorrow gets today.
364 373 const fn control_shape(kind: FieldKind) -> Control {
365 374 match kind {
366 375 FieldKind::Select => Control::Chosen,