Logseq/Entity/UI/Control
UI Control
- In this garden, UI Control pages model one thing a person operates on a product's interface — a knob, button, pad, fader, switch, field or slider — so any control can be linked by name.
What counts
Identity and names
- Place a control at
<Item>/UI/<Area>/<Kind>/<Name>, under the Logseq/Entity/UI/Area that holds it. <Kind> is the noun the product's documentation uses for that control, singular and in Title Case: Knob, Button, Switch, Toggle, Field, Slider, Menu, Pad, Fader, Marker, Jack, Strip.<Name> is the label printed on the panel or used in the manual.- On a panel mapped by position, a numbered single control carries its kind in its own name,
<Row>/<NN> <Name> <Kind>, as in Microfreak/UI/Front/Row/01 Top/02 Paraphonic Button. A control in a numbered group keeps <Group>/<Kind>/<Name>, and when the group has only one control of that kind the name is left off: Microfreak/UI/Front/Row/01 Top/01 Matrix/Knob. - A control that selects among named modes has one page per mode beneath it, and a parameter that only exists in one mode has its page beneath that mode: Logseq/Entity/UI/Control/Setting.
Page shape
- Frontmatter:
logseq-entity:: [[Logseq/Entity/UI/Control]] and up:: to its area. See Logseq/Frontmatter for shared conventions. - One bullet-wrapped H1 with the control's name and kind, then one sentence on what it does.
- A picture of the control cropped from the user guide's panel figure, kept on a Logseq/Entity/Asset/B2 page at
<Control>/Asset/Panel/png. - Optional blocks, in this order, when they apply:
- Behavior — how the control changes its value, from Logseq/Entity/UI/Control/Kind.
- Values — its range or its positions.
- Settings — links to its mode and parameter pages.
- Gestures — links to its gesture pages.
- Remote control — how another device reaches it, such as a MIDI CC number or a MIDI mapping.
- Source — the user guide or manual section that describes it.
Examples