Yeah, maybe the option to add a custom cursor when you can skip text wouldn't be a bad addition.
After some testing, I've decided call the click_delay action both on text starting and text ending, just to be sure.
But now I'm facing another tiny problem: I often use the same "display text" action part, breaking it with "<p>" tags. Unfortunately, it seems only the first block of text is unaffected, as anything following the <p> doesn't trigger a textStarted event.
As I wasn't sure I would be able to explain that accurately, I made a small demo.
The part on the bottom is what's inside the action block, in the first case one single "display text" acton part, internally divided with <p>, in the other, two distinct action parts. In both videos, I was repeatedly clicking to skip the text.https://www.youtube.com/watch?v=ZKVFcorgpAU
As you can see, the part after "hogwash" is skipped instantly in the first case (and so is the part after "Shh", which is only one action part too). In the second case, it all works swimmingly.
Will I have to break up all those occurences in multiple "display text" action parts?