Expand description
Structs§
- Against
- The part a step is edited against, as a run left it — and, for a step
of a part placed in the program, edited where it is placed, the part it
is placed in, as the step placing it left it: what the step reads there
in context (see
geop_core_program::placed::OUTSIDE). A part of its own is read as itself. - Context
- What a step is edited against: its id — what everything it builds is named after — the runner it is run by, which reads the files around its program, the part as it was before it, the part as the step built it when it last ran, if it did, and, for an event, the part as the editor draws it — what a pointer is over, without drawing it again.
- Edited
- A step’s arguments, as saved, and its editing state after an event.
- Editors
- The operations an editor offers, by name, in the order they were added:
the order an editor offers them in within a group and tier. The runner
its programs run on is given the same operations by the
crate::registry::Registrythat holds them. - Listed
- An operation as an editor lists it: the name its steps are stored
under, and its
OperationInfo. - Operation
Info - What an operation is to an editor: its short name and what it does — what an editor offers it by — and where and how prominently the editor offers it.
Enums§
- Operation
Group - What an operation works on, as an editor groups its operations: the toolbar’s sections, in this order — the order of a part’s workflow, the part’s own properties after its shape. Serialized as the group’s name, as it is shown.
- Operation
Tier - How prominently an editor offers an operation within its group, from the few used most to the rarely used: the order the group lists them in.
Traits§
- Editable
- An
Operationan editor offers: everything it keeps while a step is edited is its editing state, and everything it shows the step’s form. - Erased
Editable - An
Editablewith its types erased, so that operations of all kinds can be kept in oneEditors. Arguments come as saved.
Functions§
- forms_
built - How many forms of the step edited this thread has built
(
Editors::presentation) ever: what a test bounds the work of a pointer event by, ascrate::view::parts_drawndoes drawing — a form can ask the whole assembly about what it built. - forms_
listed - How many forms this thread has made for a list of steps
(
Editors::listed), ever: what listing the steps costs, so a test can bound it by a count rather than time it.