Any suggestions to improve the current behavior are welcome. Maybe
having a :timeout attribute would be a better solution?

Jarmo

On Tue, Jun 7, 2011 at 6:06 PM, Hugh McGowan <colinsda...@gmail.com> wrote:
> Pushed 1.9.0.rc4. The timeout for javascript_dialogs was not working well so
> I pulled this feature. Rautomation persists the timeout you set across all
> windows but with it being lazy you can't really set the timeout when you
> initialize the class and then reset it to it's original value because it
> won't get used until you try to do something (like find a button). Instead
> the user can change the timeout directly in rautomation if needed and in
> most uses the default behavior should be just fine. Currently the default
> timeout is 60s but of course the code will continue whenever the window is
> located.
>
> Thanks!
> Hugh
>
> _______________________________________________
> Wtr-development mailing list
> Wtr-development@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
_______________________________________________
Wtr-development mailing list
Wtr-development@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to