You don't know it, but this just helped me solve a completely different problem that I was experiencing with a non-Watir Ruby script.
The key was the "start". Every time I would run my Ruby script (using the "rubyw") from a batch file a command prompt window would still be left open just to annoy me. When I saw the "start" that you included below, it dawned on me that it was the batch file that was leaving the cmd window open not the Ruby interpreter.
I added that DOS command to my batch file and now the cmd window closes when the ruby script runs. Sweet! Sigh. What a relief.
Have a great weekend. Cheers! Paul C.
On 10/11/06, Cain, Mark <[EMAIL PROTECTED]> wrote:
What you're seeing is correct. What is happening with the command prompt window it is scrolling through all of the active windows objects on your machine trying to match the window title bar text. The clicker starts a new process (command prompt window) since a JS alert is modal otherwise the JS Alert would never get clicked. If the command prompt window bothers you could change the line in startClicker by adding a 'w' after ruby:
c = "start rubyw #{shortName}\\watir\\clickJSDialog.rb #{button} #{waitTime} "
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
