Page 1 of 1

Question about wait times per commands issued to eValid

PostPosted: Wed Mar 22, 2017 9:17 am
by MKleven
Morning.

Does eValid have any predefined waiting time on a command by command basis?

If so, what are they?

I hope that question isn't too vague.

Thanks

Re: Question about wait times per commands issued to eValid

PostPosted: Thu Mar 23, 2017 10:15 am
by eValid
MKleven wrote:Morning.

Does eValid have any predefined waiting time on a command by command basis?

If so, what are they?

I hope that question isn't too vague.

Thanks



Good question thanks for posting it MKleven.

No, eValid does NOT have any predefined waiting times but there are some built-in constraints.

If a command causes a navigation to occur, for example, clicking on a link to load up a new page, then the page navigation synchronization process that IS build it kicks in.

That synchronization waits for a combination of "this page is fully downloaded and ready to act upon" signals so that the next command won't wind up delivered to an empty (or partially
empty page).

See this page for some details:

http://e-valid.com/Products/Documentati ... ation.html

Otherwise, no build in delays, except as follows:

(1) You can have a fixed "wait this long before issuing the next command, no matter what (this is called the "command delay")>

(2) When eValid encounters a Delay NNN command it will wait the specified number of msec, not matter what.

(3) The Wait NNN command will wait NNN msec after first multiplying NNN by the current wait time multiplier.

If the wait time multiplier is zero you don't have any waits.

-eValid Support