Repoint three header links the conversion broke
The imports the two module headers linked through are gone, so `Meter`
and `Node::Form` are written out. `ends` had been renamed away before
this wave and nothing caught it; the two spellings meet in `narrow` and
in `axis`, one direction each.
2 files changed,
+7 insertions,
-6 deletions
| 25 |
25 |
|
//!
|
| 26 |
26 |
|
//! The shipped panel maps a value sitting on its edge to `None` and omits the
|
| 27 |
27 |
|
//! bound from the SQL: a BPM minimum of 0 is not a filter for "at least 0", it
|
| 28 |
|
- |
//! is no filter at all. Described, the same fact is an end with nothing in it,
|
| 29 |
|
- |
//! and [`ends`] is the one place the two spellings meet. Both directions, so a
|
| 30 |
|
- |
//! stored `None` comes back as an empty box rather than as the edge.
|
|
28 |
+ |
//! is no filter at all. Described, the same fact is an end with nothing in it.
|
|
29 |
+ |
//! Both directions, and one place each: `narrow` maps an end sitting on its
|
|
30 |
+ |
//! edge back to no bound at all, and `axis` carries a stored `None` out as an
|
|
31 |
+ |
//! empty box rather than as the edge.
|
| 31 |
32 |
|
//!
|
| 32 |
33 |
|
//! That is why the route reads both ends and writes both. An interval is one
|
| 33 |
34 |
|
//! answer: a handler taking only the end that moved would drop the other bound
|
| 58 |
59 |
|
//! # FINDING, second consumer: two actions over one value
|
| 59 |
60 |
|
//!
|
| 60 |
61 |
|
//! Save-as-collection takes a name and offers Save; the tag box takes a tag and
|
| 61 |
|
- |
//! offers Add. Both are a [`Node::Form`] whose submit is the only act, which is
|
|
62 |
+ |
//! offers Add. Both are a [`Node::Form`](quasi_router::Node::Form) whose submit is the only act, which is
|
| 62 |
63 |
|
//! fine, and both sit on a screen with other forms on it. `7da72faf` is the
|
| 63 |
64 |
|
//! filed shape and this is not quite it -- what is here is several forms rather
|
| 64 |
65 |
|
//! than one form with two submits -- so it is recorded rather than counted.
|
| 47 |
47 |
|
//! The one member that is genuinely droppable is the tag badges, and they
|
| 48 |
48 |
|
//! say so.
|
| 49 |
49 |
|
//! - **A hand-painted progress bar.** Twenty lines of `rect_filled`, a bevel and
|
| 50 |
|
- |
//! a click-to-seek hit test. The bar is [`Meter`]; the seek is not (see
|
|
50 |
+ |
//! a click-to-seek hit test. The bar is [`Meter`](quasi_router::Meter); the seek is not (see
|
| 51 |
51 |
|
//! below).
|
| 52 |
52 |
|
//!
|
| 53 |
53 |
|
//! # THE FINDING: `Meter` refuses the second of the two proportions here
|
| 55 |
55 |
|
//! This band has two, and the vocabulary treats them differently:
|
| 56 |
56 |
|
//!
|
| 57 |
57 |
|
//! - **Analysis coverage** — "142/200 analyzed" — is a proportion of a set and
|
| 58 |
|
- |
//! exactly what [`Meter`] was added for. No argument.
|
|
58 |
+ |
//! exactly what [`Meter`](quasi_router::Meter) was added for. No argument.
|
| 59 |
59 |
|
//! - **Playback position** is refused by `Meter`'s own header: "This is a
|
| 60 |
60 |
|
//! proportion of a set and not the progress of an operation. A running timer
|
| 61 |
61 |
|
//! or a fetch is imperative and live, and a screen is described once per
|