unable to located object in general means that the page has not yet load (as
far as I understand it. Instead of sleep (which just slows down everything) try
wrapping your code as follows. (The below is just an example, and only my
opinion. I'm sure there are 1000 better ways of doing this) :)
Without a sufficient delay (in this case 10 seconds), checkboxes are not
recognized in the modal dialog - running (nodebug) in Eclipse or running from
the command line.
This workaround is simple and acceptable short term. Would retry logic in watir
be a possible long term solution?
Timing issues are by far my biggest headache too.
I did see a patch (never tried it) that would handle recursive frame waits (or
something like that). Not sure if that would handle modal issues.
-
Posted via Jive Forums
John Lolis wrote:
unable to located object in general means that the page has not yet load (as
far as I understand it.
I agree that this is probably the reason for the Dave's problem.
Specifically the wait logic that normally occurs in Watir, does not
work in modal_dialogs (and is thus not
I am navigating a modal dialog with radio buttons, buttons, and checkboxes.
Everything works when I run in debug mode (using Eclipse). When I run nondebug,
the checkbox identifiers (by id) are not recognized. Example code:
ie.modal_dialog.checkbox( :id, 'inpCheckBoxDC_19' ).set
I'll answer my own question. If the code sleeps long enough, in this case 10
seconds, the checkboxes are recognized and set. This seems to be the common
cure for Modal dialog-itis
-
Posted via Jive Forums
Are you seeing this problem when you run in Eclipse? Does the same thing
happen when you run outside of eclipse? (like from the command line?)
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
