Jarmo - I think I eventually tried the 2nd option which is why I knew it wasn't finding the link. That's a good trick replacing start rubyw with ruby -e...I'll have to try that.
Alan On Feb 8, 2010 3:44 AM, "Jarmo Pertman" <[email protected]> wrote: Hello. unique_number is an method for Watir::Element and it's declaration is (for Watir 1.6.2) at element.rb on line 88 - in short, it is just a wrapper for ole_object.invoke('uniqueNumber'). For debugging the reason of the failing of click_no_wait, I'd suggest you to modify method called eval_in_spawned_process which is declared in page_container.rb on line 50. Instead of line: exec_string = "start rubyw -e #{(load_path_code + '; ' + ruby_code).inspect}" try: exec_string = "ruby -e #{(load_path_code + '; ' + ruby_code).inspect}" Then you should see the error message (if any) on your console. If that doesn't help, then you could also add this line just before system(exec_string): File.open("c:/click_no_wait.txt", "w") {|f| f.puts exec_string} Now open the text file and execute this long command from your command line directly to see if you get any error messages or if anything happens. You could modify this command to output some additional debug information like browser url, browser title or html or whatsoever so you know that it can attach to correct window (and not to that other tab for example). Hopefully it helps. Jarmo On Feb 5, 8:50 pm, Alan Baird <[email protected]> wrote: > Yeah...I know, you all probabl... -- You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to [email protected] Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/watir-general
