Struct Section 

pub struct Section {

    pub title: String,
    pub subtitle: Option<String>,
    pub origin: Option<&'static str>,
    pub root: Option<PathBuf>,
    pub rows: Vec<Entry>,
    pub door: Option<Entry>,
    pub unavailable: bool,
    pub unavailable_note: Option<String>,
    pub folded_by_default: bool,
    pub remote_root: Option<PathBuf>,
    pub waiting: bool,
    pub grouped_by_place: bool,
    pub place_labels: HashMap<PathBuf, String>,
}

A titled group of rows on the home screen.

Fields

title: String

subtitle: Option<String>

How the section is doing, at the far end of the rule: the filesystem it is on, first 5000 for a listing cut short, what a search covered. Never why the section exists; that is origin.

origin: Option<&'static str>

Why a path-titled section is here — current directory, configured — as a chip beside the count, where the eye is. It used to share the note slot at the far right with the state, and a directory derived from a recent was drawn exactly like a configured one with only that word to tell them apart.

root: Option<PathBuf>

The directory a path-titled section lists: a root, or the directory browsed. The title is abbreviated for display and cannot be turned back into a path.

rows: Vec<Entry>

door: Option<Entry>

The row that opens the directory this section lists, as one table. Its own row, not one of rows.

Kept apart because its path is the directory’s — with a trailing slash, which PathBuf compares and hashes away — so as a row among the others it was the same key as the directory’s row one level up in every path-keyed map. That cost a real bug once: measuring the door wrote a kind-less measurement into the directory’s slot, the directory upstairs was then taken for already looked into, and it kept Unknown — no label, no holds line, no place in the count — for the rest of the session. A guard per walker would have to be added again by every walker written after it, so the collision is gone instead: nothing that walks rows or matches Row::Entry can reach the door.

unavailable: bool

Set when a root could not be read, so the UI can say why it is empty.

unavailable_note: Option<String>

What to say instead of the bare word “unavailable”.

A share that has stopped answering has nothing to add: “unavailable” is the whole story. A bucket listing that was refused does — “403, no storage.buckets.list access” tells the user what to change, and an empty section that does not say why tells them nothing.

folded_by_default: bool

Starts folded unless the user has opened it. For the places that are context rather than the reason you came: directories promoted from recents, and the desktop’s list of where you have been.

remote_root: Option<PathBuf>

The remote root whose background probe fills this section in.

waiting: bool

The probe had not answered when this listing was built, so the rows are not in yet. Shown, not hidden: an empty section here means “wait”, not “nothing”.

grouped_by_place: bool

Rows are shown under the place each lives in, with a row for the place itself. Set on RECENT, whose rows come from anywhere; a directory’s rows all live in the directory the title names.

place_labels: HashMap<PathBuf, String>

What the dataset index remembers each place to be, for the place rows of a grouped section. Filled from the cache when the listing is built, never by reading a place.

Trait Implementations

impl Clone for Section

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Section

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.