main
tag: v0.10.0
tag: v0.11.0
tag: v0.12.0
tag: v0.13.0
tag: v0.14.0
tag: v0.14.1
tag: v0.15.0
tag: v0.16.0
tag: v0.16.1
tag: v0.17.0
tag: v0.18.0
tag: v0.19.0
tag: v0.20.0
tag: v0.21.0
tag: v0.22.0
tag: v0.23.0
tag: v0.24.0
tag: v0.25.0
tag: v0.25.1
tag: v0.26.0
tag: v0.27.0
tag: v0.28.0
tag: v0.29.0
tag: v0.30.0
tag: v0.31.0
tag: v0.32.0
tag: v0.33.0
tag: v0.34.0
tag: v0.35.0
tag: v0.36.0
tag: v0.37.0
tag: v0.38.0
tag: v0.39.0
tag: v0.40.0
tag: v0.41.0
tag: v0.41.1
tag: v0.42.0
tag: v0.43.0
tag: v0.44.0
tag: v0.44.1
tag: v0.44.2
tag: v0.5.0
tag: v0.5.1
tag: v0.6.0
tag: v0.7.0
tag: v0.8.0
tag: v0.9.0
Files
Commits
Tags
Notes
Issues
Follow makeover-layout to 0.43.0
`links = "makeover-layout"` forbids two copies of the vocabulary in one
graph, so every consumer moves in the same wave.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session
https://claude.ai/code/session_01MptwXZ8k65v19rFmdGAyki
2 files changed,
+2 insertions,
-2 deletions
20
20
# compile against an API added in a later one -- which is what `Depth::Overlay`
21
21
# would do here. The rest of the suite has pinned this way since
22
22
# makeover-webview found it the hard way.
23
-
makeover-layout = "0.42"
23
+
makeover-layout = "0.43"
24
24
# The cadence the activity mark blinks at, and the motion-off seam beside it.
25
25
# Taken rather than chosen here: `activity_lit` is this crate's only use of it,
26
26
# and the whole point is that the number is not this crate's to pick.
83
83
//! # `piece`, not `widget`
84
84
//!
85
85
//! `makeover-layout` owns `Region::Widget`, the tier between a primitive and
86
-
//! `Region::Bespoke`: a named assembly of primitives that each renderer draws
86
+
//! `Region::Widget`: a named assembly of primitives that each renderer draws
87
87
//! its own way. That is host-agnostic and sits *above* every renderer.
88
88
//!
89
89
//! This crate's [`piece`] module is the opposite end of the same stack: