Working out what is happening when your script is failing in this
instance was time-consuming and non-obvious. I assume that Watir's
audience includes people who may not figure out what is going on when
their script appears to randomly fail. It makes sense to me to prevent
this problem if it can be done without much of an impact on performance.
Jared
Lonny Eachus wrote:
Apologies for the post with the wrong subject line . . .
By automatically, I would hope you mean a kind of "wait_for()" method,
rather than doing it unseen in the background. At first thought it
seems the latter would be terribly inefficient, especially since it is
only necessary in relatively rare cases.
Time and efficiency are definitely a concern in our screen scrapes. I
was already considering overriding existing delays in the code. If this
loop were done every time, we would likely be in the position of having
to go into the Watir code to take it back out, in order to regain what
efficiency we could.
Lonny Eachus
On 6/7/06, Lillis, Dara <[EMAIL PROTECTED]>
wrote:
while
not ($ie.link(:text,"Second").exists?)
sleep 0.5
end
$ie.link(:text,"Second").click
This is what i do as well.
I
think the remaining question is whether Watir should do this
automatically. I've actually coded this directly and tested it and it
works. It's only a couple of lines of code.
. . .
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
|
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
