KFC thanks, I get it now.
Same example as above- a simple rotating slide effect...
Begin by making a global variable. (Mine is SLIDECOUNT, set to 0.)
Set up the time frame that you wish your slide to rotate. I want my frame to last for 3 seconds, then rotate clockwise for the duration of 1 second.
System / Every 3 seconds
ADD 1 to SLIDECOUNT
System WAIT 1 Second
SUBTRACT 1 from SLIDECOUNT
This Action simply causes the SLIDECOUNT variable to change from 0 to 1 for 1 second every three seconds.
Now we just have to tell the system what to do during the one second that SLIDECOUNT is going to be equal to 1. We can do that using the System / Compare Variable option.
System / SLIDECOUNT = 1
SLIDECOUNT / Rotate Clockwise 1?.
And that's it.
When you run that, the system will wait for three seconds, start rotating your slide by 1?, and for the the duration of SLIDECOUNT=1, it will just keep rotating by a single degree.
Lol... I was making it waaaaay harder than it needed to be.
Nothing against the seasoned vets, but...
You could use the Wait action.
-> Toggle Boolean/variable
-> Wait x seconds
-> Toggle Boolean/variable back to original
That way you will be able to use the variable to execute an action for a set amount of seconds.
... sometimes the psuedocode can be a bit vague. Structuring things closer to syntax really helps. I never would have imagined that it would have required multiple actions to achieve this particular task from KFC's psuedocode, which is grouped together like a paragraph, and leads one to believe that it could all be placed in one Action.
I'm not complaining, just trying to explain why it seems like we're asking the same question five times! ^__^