The case I have encountered for using click!, is when 'click' doesn't
return for a long time (or sometimes never depending on how buggy a
web page or ad-servers are), and a 'click!' followed by a 'wait_until'
to check the event success/fail is sufficient.
--Shane.
On Oct 13, 12:44 pm, Bret
recommend you use click!,
because you don't have the overhead of starting up a new ruby process
each time.
And that has worked for me so far.
I haven't used fireWatir, so can't answer for how that operates.
Thanks,
Shane.
On Oct 11, 9:57 pm, Pallavi Sharma write2pall...@gmail.com wrote:
Hi
We
, and modify the 'eval_in_spawned_process'
Watir function to use this handle for 'pc = Watir::IE.bind
(iWebBrowserPtr)'.
This now works fine. :)
On Sep 28, 12:34 pm, Bret Pettichord bpettich...@gmail.com wrote:
Shane,
Thanks for the excellent description of the problems that occur when
your
:in
each
Which contains:
c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:246
shell = WIN32OLE.new(Shell.Application)
windows = shell.Windows ## Fails here
Let me know if I can supply more details or disambiguation! :)
Thanks, Shane
