Of course you are right. The patch was attached to this email: 
http://rubyforge.org/pipermail/wtr-development/2009-January/000400.html

It seems like this has not been put into Jira yet.

Bret

lokesh.agra...@gmail.com wrote:
> I applied the patch but still the same issue.
> This patch is for winClicker.rb I don't know how it's going to affect
> click_no_wait method.
>
> Can anyone please help me out.
>
>
> Thanks and Regards,
> Lokesh Agrawal
>
>
> On Feb 2, 9:08 pm, Bret Pettichord <b...@pettichord.com> wrote:
>   
>> http://jira.openqa.org/browse/WTR-279
>>
>> lokesh.agra...@gmail.com wrote:
>>     
>>> Hi Bret,
>>>       
>>> Can you please tell me from where I can get the patch?
>>>       
>>> Thanks and Regards,
>>> Lokesh Agrawal
>>>       
>>> On Jan 20, 7:53 am, Bret Pettichord <b...@pettichord.com> wrote:
>>>       
>>>> A patch that fixes this problem was recently submitted to the
>>>> wtr-development list.
>>>>         
>>>> Bret
>>>>         
>>>> jensen2525 wrote:
>>>>         
>>>>> I ran into this issue and have been able to resolve what was causing
>>>>> this on Windows XP.  This maynotbe what's causing it for other folks
>>>>> but hopefully it will point them in the right direction.
>>>>>           
>>>>> We have an TeamCity server that will execute our tests using Rake on
>>>>> the build agents running Windows XP.  When my scripts that were
>>>>> dealing with popups ran on the agents they failed every time with the
>>>>> same issue described in this thread.
>>>>>           
>>>>> So what I did was take the simple Google sample and run it in a
>>>>> Command Prompt on the agent directly and it worked fine.  I used the
>>>>> Command Prompt window and executed my full test case and it ran fine.
>>>>> I shut down the TeamCity build agent service, and ran their agent
>>>>> batch files directly (notthe service).  I kicked the build off again
>>>>> and it ran fine this time.
>>>>>           
>>>>> The problem seemed to be related to the Ruby process executing under
>>>>> the SYSTEM user account.  I stopped running them through the service
>>>>> and instead as normal batch files in the Startup and they're working
>>>>> fine now.  It seems like there is an issue related to the
>>>>> @page_container.eval_in_spawned_process when running under this type
>>>>> of security setup.  Make sure whatever process is launching Ruby is
>>>>> running as a normal user account and see if that resolves the problem.
>>>>>           
>>>>> Hope this helps.
>>>>>           
>>>>> On Dec 12 2008, 9:19 am, Bret Pettichord <b...@pettichord.com> wrote:
>>>>>           
>>>>>> Your code is correct. There is something about your configuration that
>>>>>> causes this to fail.
>>>>>>             
>>>>>> Bret
>>>>>>             
>>>>>> HAHAHA wrote:
>>>>>>             
>>>>>>> I have tried, using this code:
>>>>>>>               
>>>>>>> require 'watir'
>>>>>>>               
>>>>>>> browser = Watir::IE.new
>>>>>>> browser.goto('http://www.google.com')
>>>>>>> browser2 = Watir::IE.attach(:title, /Google/)
>>>>>>> browser2.text_field(:name, 'q').set('Watir')
>>>>>>> browser2.button(:name, 'btnG').click_no_wait
>>>>>>>               
>>>>>>> The click_no_wait still cannot run. Is the code right?
>>>>>>>               
>>>>>>> On Dec 12, 9:58 am, "larryni...@gmail.com" <larryni...@gmail.com>
>>>>>>> wrote:
>>>>>>>               
>>>>>>>> Pramod, could you show us an example of your code?
>>>>>>>>                 
>>>>>>>> On Dec 11, 11:01 pm, "pramod D" <petkar.pra...@gmail.com> wrote:
>>>>>>>>                 
>>>>>>>>> Hi Michael,
>>>>>>>>>                   
>>>>>>>>> Initially i also faced same problem when i use Click_no_wait control 
>>>>>>>>> was
>>>>>>>>> going but never clicked it, To come around this initially i opened 
>>>>>>>>> the IE
>>>>>>>>> (IE7)with blank page and then, i will attach the browser at the start 
>>>>>>>>> of the
>>>>>>>>> script and continue to execute my script as usual and worked 
>>>>>>>>> correctly. For
>>>>>>>>> time being you can fallow this turn around method.
>>>>>>>>>                   
>>>>>>>>> Thanks,
>>>>>>>>> Pramod
>>>>>>>>> On Fri, Dec 12, 2008 at 1:46 AM, Michael Hwee 
>>>>>>>>> <michael_h...@yahoo.com>wrote:
>>>>>>>>>                   
>>>>>>>>>> That is disappointing.
>>>>>>>>>> I believe that is something like OS and/or configuration issues, 
>>>>>>>>>> rather
>>>>>>>>>> than watir itself.
>>>>>>>>>>                     
>>>>>>>>>> Michael
>>>>>>>>>>                     
>>>>>>>>>> ----- Original Message ----
>>>>>>>>>> From: "larryni...@gmail.com" <larryni...@gmail.com>
>>>>>>>>>> To: Watir General <watir-general@googlegroups.com>
>>>>>>>>>> Sent: Thursday, December 11, 2008 12:00:00 PM
>>>>>>>>>> Subject: [wtr-general] 
>>>>>>>>>> Re:button.Click_No_Waitonlyhighlightsthebutton,
>>>>>>>>>> doesnotclick
>>>>>>>>>>                     
>>>>>>>>>> Sorry, Michael, your code doesn't work either.  It opens the page,
>>>>>>>>>> highlightsthebuttonyellow, and then just sits there.  No popup is
>>>>>>>>>> ever launched because it doesn't actuallyclickthebutton.  Watir
>>>>>>>>>> doesn't report any errors, but it never completes, either.  If I
>>>>>>>>>> change click_no_wait toclick!, itdoeslaunch the popup, but the
>>>>>>>>>> handle_nextpopup command never executes - it's been sitting here for
>>>>>>>>>> 90-120 seconds with the popup opennotdoing anything.  So, again, to
>>>>>>>>>> summarize: click_no_wait is incapable of firing any events, butclick!
>>>>>>>>>> makes the script hang.- Hide quoted text -
>>>>>>>>>>                     
>>>>>>>> - Show quoted text -
>>>>>>>>                 
> >
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To post to this group, send email to watir-general@googlegroups.com
Before posting, please read the following guidelines: 
http://wiki.openqa.org/display/WTR/Support
To unsubscribe from this group, send email to 
watir-general-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/watir-general
-~----------~----~----~----~------~----~------~--~---

Reply via email to