From: Chris Morris Date: 2003-03-11T22:45:19+09:00 Subject: Re: Killing an WIN32OLE IE Object I don't know if this is what you're looking for, in my ClIEController[1] lib, to wait until it's *really* done loading the current page, you must (1) wait for the busy property to be false (2) wait for the ReadyState property to equal READYSTATE_COMPLETE [1] http://clabs.org/ruby.htm As far as the caching issues you talked about -- the best I've done so far with my acceptance testing is to manually set the browser options to load the page fresh each time *and* delete everything in the Temporary Internet Files during tear down. The options to load fresh each time can be found here: Tools -> Options... -> General tab -> Temporary Internet Files section -> Settings... Technically, the Navigate method in the COM interface takes an argument where you can specify it not load the document from the cache -- but in playing with this it doesn't seem to work at all. Chris ----- Original Message ----- From: "Eric Hodel" To: "ruby-talk ML" Sent: Monday, March 10, 2003 5:22 PM Subject: Killing an WIN32OLE IE Object To get to the point, how can I force a WIN32OLE object to wait until a method completes properly? (specifically ie.quit) -- Eric Hodel - drbrain@segment7.net - http://segment7.net All messages signed with fingerprint: FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04