Documentation
¶
Overview ¶
Package listselect owns one concern: the multi-selection mode a record list enters when its host is about to act on several rows at once. It is a lego piece — targetlist and targetdate assemble it, they do not re-declare it.
Sibling of listgap, and for the same reason: two lists that must stay visually and behaviourally interchangeable (crudview swaps one for the other) cannot each own a private copy of the rule.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type Mode ¶
type Mode struct {
// OnChange fires after every toggle with the current count, so a host can
// label its commit button ("🗑 3") and disable it at zero.
OnChange func(n int)
// contains filtered or unexported fields
}
Mode is the selection state of one list. The zero value is a usable list in normal mode — a list is a list until its host says otherwise.
func (*Mode) CheckedIDs ¶
CheckedIDs returns the marked ids in the order given by ids, which the caller passes as its current render order.
Ordering is NOT optional and NOT the caller's problem to remember: checked accumulates in TAP order, and a host building a confirmation message from tap order would list rows in an order that matches nothing on screen. Taking the render order as a parameter is what makes the wrong version unwritable — there is no accessor that returns the raw slice.
func (*Mode) On ¶
func (m *Mode) On() *SignalBool
On reports the signal a component binds its root state to, so the stylesheet can reveal the checks. Never a bool: the skin has to react.
Source Files