Ah. Thanks for the info. I haven't noticed that problem/error before on my
system that's running Ruby 184-20 and Watir 1.4.1, so I never really looked
closely at what the underlying calls are.
As far as I'm concerned, if it works don't look any further. ;-)
Good luck. Paul C.
On 07/02/07, Nathan Christie <[EMAIL PROTECTED]> wrote:
When I use this Watir command you have suggested, it unwraps it and sends
essentially the WIN32OLE command to create a new IE instance, so in turn:
[ myIE = IE.new() ] == [ myIE = WIN32OLE::new( "
InternetExplorer.Application" ) ]
So this Watir command: `IE.new()` does this:
IE.new() —› IE object constructor: `initialize()`
—› `initialize()` calls `create_browser_window()` —›
`create_browser_window()` executes this command: [EMAIL PROTECTED] =
WIN32OLE.new('
InternetExplorer.Application')`
Having used Ruby's WIN32OLE library for some years to automate MS apps, I
wanted to see what the error would be like if I used that code. The error
you get back from Watir is different and IMO not as informative as the one
you get from Ruby when executing the initialization code that throws the
error.
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
