There is no stack dump or exception, all I get is the window I posted which blocks execution untill I quit the window - nothing is given on the command line. I suppose there might be some logs somewhere, I'll have a dig around.
On Tuesday, 9 October 2012 04:17:12 UTC+13, Jarmo Pertman wrote: > > What is the exact crash message when you run the command printed out by > $DEBUG on your command line? > > Jarmo Pertman > ----- > IT does really matter - http://itreallymatters.net > > > On Monday, October 8, 2012 6:36:41 AM UTC+3, Paul wrote: >> >> Ok, does no crash on my VM so its something to do with my PC environment. >> >> On Monday, 8 October 2012 16:17:00 UTC+13, Paul wrote: >>> >>> I see now that click_no_wait is run from method_missing in element.rb. >>> >>> I turned on DEBUG, grabbed the spawned process command and ran it at the >>> command prompt. >>> >>> ruby -e >>> "$:.unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-classic-3.2.0/lib/watir-classic/win32ole/1.9.3').unshift('C:\\Users\\pauld\\workspace\\SopranoMedicalRecords\\AutomatedTests\\med_rec\\').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/ffi-1.1.5-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/win32-process-0.7.0/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/win32-api-1.4.8-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/windows-api-0.4.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/windows-pr-1.2.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/nokogiri-1.5.5-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/rautomation-0.7.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/xml-simple-1.1.1/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/hoe-3.1.0/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/s4t-utils-1.0.4/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/builder-3.1.3/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/user-choices-1.1.6.1/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/yajl-ruby-1.1.0-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/subexec-0.0.4/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/mini_magick-3.2.1/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/win32screenshot-1.0.7/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-classic-3.2.0/lib').unshift('c:/Ruby193/lib/ruby/site_ruby/1.9.1').unshift('c:/Ruby193/lib/ruby/site_ruby/1.9.1/i386-msvcrt').unshift('c:/Ruby193/lib/ruby/site_ruby').unshift('c:/Ruby193/lib/ruby/vendor_ruby/1.9.1').unshift('c:/Ruby193/lib/ruby/vendor_ruby/1.9.1/i386-msvcrt').unshift('c:/Ruby193/lib/ruby/vendor_ruby').unshift('c:/Ruby193/lib/ruby/1.9.1').unshift('c:/Ruby193/lib/ruby/1.9.1/i386-mingw32');require >>> >>> 'c:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-classic-3.2.0/lib/watir-classic/core';Watir::Button.new(Watir::IE.attach(:hwnd, >>> >>> 922786).frame({:tag_name=>['frame', 'iframe'], :id=>'viewIFRAME'}), >>> :tag_name => Array.new << 'button' << 'submit' << 'image' << 'reset', >>> :unique_number => 1).click!();" >>> >>> >>> >>> Again so we can see all the info: >>> >>> >>> >>> >>> Looks like that process is crashing. Anyone else have that problem? >>> Maybe it is something with my environment - will set up a VM and try that. >>> >>> I will keep debugging this, it is crucial I solve this. I am handing >>> over the framework I wrote to my collegues as I start a new job next week. >>> >>> Any help is appreciated. >>> >>> On Friday, 5 October 2012 09:52:31 UTC+13, Paul wrote: >>>> >>>> Hi, I have just upgraded my framework to 1.9.3 and watir 4.0, I am >>>> using watir-classic 3.2.0. I have been using click_no_wait but now it does >>>> not work and I can't find the method in the source. element.rb no longer >>>> has this method! >>>> >>>> If I can't solve this I will try to patch it in or downgrade watir. >>>> >>>> - thanks >>>> >>> -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
