| 91 |
91 |
|
//! and `Cells` deliberately had no tick: its doc said "no table asks for one,
|
| 92 |
92 |
|
//! and a member added because its sibling has it is a member with no consumer
|
| 93 |
93 |
|
//! to tell us what it should mean." This screen asked, and asking turned out to
|
| 94 |
|
- |
//! need two members rather than one — [`Cells::ticking`], and [`Field::over`],
|
| 95 |
|
- |
//! because a bulk bar is not only buttons. See [`bulk`] for what the bar holds
|
| 96 |
|
- |
//! and [`View::ticked`] for why select-all is an address.
|
|
94 |
+ |
//! need two members rather than one: [`Cells::ticking`], and a `Field::over`
|
|
95 |
+ |
//! that has since been removed, because a bulk bar is not only buttons. The
|
|
96 |
+ |
//! picker half is said with [`Act::asks`] now. See [`bulk`] for what the bar
|
|
97 |
+ |
//! holds and [`View::ticked`] for why select-all is an address.
|
| 97 |
98 |
|
//!
|
| 98 |
99 |
|
//! What is still not sayable is the **count**: `tasks.js` writes "3 selected"
|
| 99 |
100 |
|
//! into the bar and hides the bar when nothing is ticked. The ticks are the
|
| 742 |
743 |
|
/// and carry no value; priority, project and snooze apply a value, and reach it
|
| 743 |
744 |
|
/// through [`Act::asks`] rather than by being pickers that write as they change.
|
| 744 |
745 |
|
///
|
| 745 |
|
- |
/// The picker was the reason [`Field::over`] was added: said as plain acts, a
|
| 746 |
|
- |
/// project picker is one button per project. `Act::asks` answers that without
|
|
746 |
+ |
/// The picker was the reason a `Field::over` member once existed: said as plain
|
|
747 |
+ |
/// acts, a project picker is one button per project. `Act::asks` answers that
|
|
748 |
+ |
/// without
|
| 747 |
749 |
|
/// the write, because the value rides with the press instead of firing on its
|
| 748 |
750 |
|
/// own, so a picker over forty projects is still one control. Under
|
| 749 |
751 |
|
/// wiki `explicit-commit-affordance` the press is also the commit the reader
|