Okay, let's see if I can summarize this without tieing myself in knots:
1. randomtimer() is, as the name suggests, random. A randomtimer() will set off an alarm() at a random interval between the time values given.
2. Kiss viewers interpret fkiss commands/events in the order listed in the cnf. However, they still do this very fast; it may make a difference to the computer, but rarely will the user notice this.
If you have several randomtimers, each tied to different events then it shouldn't be noticeable by you that one is triggering before the others, assuming the timers are all of similar values. Where it is noticeable is when you have several short randomtimers all triggered from the same event, designed to result in multiple possible outcomes to said event, like the die roll I mentioned earlier. My kis mentor refered to this as "racing timers", extremely suitable description if you ask me.
In the instance you mention; three dolls, each with their own rate of blinking, the issue of when timers are set off shouldn't be a problem. The time difference from one to the next setting off should be measured in fractions of a second, to fast to register on the human eye. Then again, as they're meant to be blinking at different rates you hardly want them to start at the same time do you?
Posted on Mar 19, 2002, 6:18 AM from IP address 210.84.117.114
