Checkpoint ink architecture updates
This commit is contained in:
@@ -140,7 +140,7 @@ Tag format:
|
||||
|
||||
For Ink choices, put choice-local tags under the choice they belong to. Explicit keyboard letters are supported with `# letter[x]`, `#letter[x]`, or the colon form `#key:x`; the client reserves those keys first, then assigns the remaining visible choices from `1` through `0`, then `A` through `Z` in visible order. `#optional` renders the choice in italic. `# action[name]` or `#action:name` assigns an invisible action group: group order follows the first appearance of each action tag in the authored list, entries inside each group are randomized, and choices without an action tag are grouped last.
|
||||
|
||||
`#auto` marks an Ink choice that the browser should choose automatically instead of rendering as a visible button. The choice should usually omit visible `[...]` text. `#auto(2)` waits two UI choice turns since the last global auto trigger. `#auto[keyword](2)` waits two UI choice turns only since the last auto trigger with the same keyword.
|
||||
`#auto` marks an Ink choice that the browser should choose automatically instead of rendering as a visible button. Auto choices still need a developer-facing bracket choice text so they remain testable in Inky. `#auto(2)` waits two UI choice turns since the last global auto trigger. `#auto:keyword(2)` waits two UI choice turns only since the last auto trigger with the same keyword. Use the colon form for keyed auto tags on choice lines.
|
||||
|
||||
Chapter:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user