@@ -4582,7 +4582,7 @@ <h2>Parallel Actions</h2>
4582
4582
< p > The diagram below displays when each action gets executed.
4583
4583
"Source 1" is the first finger, and "source 2" is the second.
4584
4584
4585
- < p > < img src =" svgs /note1actions.svg" alt ="">
4585
+ < p > < img src =graphics /note1actions.svg alt ="">
4586
4586
4587
4587
< p > There is no limit to the number of input sources,
4588
4588
and there is no restriction regarding the length of each input's action list.
@@ -4627,7 +4627,7 @@ <h2>Parallel Actions</h2>
4627
4627
4628
4628
< p > And the execution of each action will be done as follows:
4629
4629
4630
- < p > < img src =" svgs /note4actions.svg" alt ="">
4630
+ < p > < img src =graphics /note4actions.svg alt ="">
4631
4631
4632
4632
< p > Specific timing for the actions can also be expressed.
4633
4633
The "pause" action can be used to either a) indicate
@@ -4638,7 +4638,7 @@ <h2>Parallel Actions</h2>
4638
4638
for the longest pause to complete.
4639
4639
For example, in this diagram:
4640
4640
4641
- < p > < img src =svgs /note2actions.svg alt ="">
4641
+ < p > < img src =graphics /note2actions.svg alt ="">
4642
4642
4643
4643
< p > The remote end will dispatch the pointerDown actions in the first tick.
4644
4644
In the second tick, since source 1 declares a pause of 5 seconds,
@@ -4654,7 +4654,7 @@ <h2>Parallel Actions</h2>
4654
4654
then the input source will not have any actions executed in the containing tick.
4655
4655
As an example:
4656
4656
4657
- < p > < img src =" svgs /note3actions.svg" alt ="">
4657
+ < p > < img src =graphics /note3actions.svg alt ="">
4658
4658
4659
4659
< p > During tick 2, source 1 will have its pointerMove action dispatched,
4660
4660
while source 2 will do nothing.
0 commit comments