| || |
DelayFor NOT executed
User =?iso-8859-1?Q?=C9ric_Hamel?= (firstname.lastname@example.org) posted:
Could it be...
In Robot, look at Tools->GUI Playback Options, Diagnostic Tools tab: Set
Timeout Multiplier Value.
In 2000, this parameter was disabled. In 2001, it defaulted to 10, which
would multiply all timeout values by 10 (that explains why a 10 second
timeout would consistently take 1:40 minute to get declared in my script).
If you have set this value to 0, I wonder what effect this would have...?
In 2001A, I'm not sure what the default value is. Mine is set to 1. Could
it be a leftover from my old installation, or did they change the default to
1, which they were supposed to do...?
Now, does this parameter affect the DelayFor instruction??? Dunno!
129, avenue de la Drave
Gatineau (Québec), J8T 7V5
Courriel: email@example.com <mailto:firstname.lastname@example.org>
Cellulaire: 613-852-1174 Fax: 819-246-9257 Maison: 819-561-8727 e-Fax:
Re: DelayFor NOT executed
User MArk B. (email@example.com) posted:
HEY! That was my idea!
Not saying that I'm the only one that came up with it. Just that I came up
with it without anyone else's help.
You can use the multiplier to handle different playback speeds caused by
running scripts on slower machines.
Wish I could go to 2001 :-(
Divide by zero maybe?
"Éric Hamel" <firstname.lastname@example.org> wrote in message