Ph0enixAsh wrote:Unknown Elements
must(self:
mustnot(self:
goto(target: as opposed to go(target:
instruc(set:
instruc(unset:
instruc(mult:
Unknown delay attributes
delay( time="", start-with="", target="", onTriggered="", style="" )
go(
target) creates a Continue button while
goto(
target) immediately redirects to the target without user interaction.
The
instruc and
action parts of a
page(
text?,
media?,
action?,
hidden?,
instruc?) show up in the sidebar, while
media and
text (not to be confused with
text(
text)) represents the main content.
Almost anywhere you can use
[vert|horiz|mult](
e0..) to stack elements vertically, horizontally or on top of each other. Understandably stacking of non-visual elements is usually done with
mult.
There is no such
start-with and/or
onTriggered in
delay(
time,
target,
style?). Also these arguments don't seem to be used in any tease. But it's not a problem, the viewer ignores all unknown codes and arguments.
PCM2
must(
self,
action0..) creates a PCM2-must relationship for
self. Meaning all
actionX actions must be "set" (see below) for the
self action (usually a page) to be runnable.
On the other hand
mustnot(
self,
action0..) makes
self unavailable if any
actionX action is set.
set(
action0..) sets actions,
unset(
action0..) unsets actions. What more can I say? Initially all actions can run only once. When you run it, it gets set, so next time you try running it it would get skipped. But you can also
set it programmatically, for example to skip it without having ever been run. And on the other hand you can
unset it to make it runnable. On top of that you can use
repeat[add|del|set](
target,
count) to change the number of runs for an action to
actually be regarded as set. (Not to be confused with
repeat(
count,
max?).) In the end this boils down to two variables, number of runs and repeats, which you can use to ignore an action if its runs >= its repeats. And the only command that even pays attention to this constraint is
range(
from,
to,
prefix?). Same goes for
numactions(
self,
count) and
numactionsfrom(
self,
count,
since), which make an action only available after a certain
count of actions have been run (optionally counting from the first run of some
since action).
