Hi all, Thanks for all the posts. I am not really trying to access the button by using unique_number. The click_no_wait function in element class passes the command to spawned_click_no_wait_command which refers to the element using unique_number.
I have seen the example on the page: http://wiki.openqa.org/display/WTR/Modal+Dialogs. And, there is not problem of page hanging up after click_no_wait is used to click on button for modal dialog. So, in this case, WATIR is able to access the button using unique_number. However, in my case it is not. Also, I verified that click_no_wait is using the correct hwnd. I have no clue what to do with this. Kushal On Dec 3, 7:03 am, Arto Vuori <[email protected]> wrote: > You're right, I don't really need to do that. Thanks for helping out! > > --A. Vuori > > On 1 joulu, 10:38, Jarmo Pertman <[email protected]> wrote: > > > Why are you running your tests in $DEBUG mode anyway? There should be > > a lot of information in your console if $DEBUG is enabled all the > > time. Do you really need it? It seems to me that you're just doing it > > wrong if it's enabled for your whole testsuite... > > > You can monkey-patch that if it's really needed: > > > module Watir > > class Element > > def spawned_click_no_wait_command(command) > > command = "-e #{command.inspect}" > > "start rubyw #{command}" > > end > > end > > end > > end > > > Jarmo Pertman > > ----- > > IT does really matter -http://www.itreallymatters.net > > > On Nov 30, 8:36 am, Arto Vuori <[email protected]> wrote: > > > > Ah, there seems to be a design decision between debugging > > >click_no_waitoutput and breaking the method in debug mode. The latter > > > was confusing, the former was on the other hand very helpful > > > initially. Could there be another way of debugging the output of > > >click_no_wait, as now it is not possible to run tests (that are using > > >click_no_wait) in debug mode at all? Therefore, I must leave my change > > > in place. > > > > --A. Vuori > > > > On 30 marras, 02:27, Jarmo Pertman <[email protected]> wrote: > > > > > Arto Vuori: > > > > #click_no_waitis only blocking intentionally when $DEBUG is true. As > > > > soon as you use it normally (e.g. $DEBUG being false) then "start > > > > rubyw" is used to perform the click itself thus the change made by you > > > > should not be needed and it should work without that either. Just make > > > > sure that $DEBUG is not true :) -- 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]
