Something occured to me last night; I had installed DevKit, which was required to get the FastDebugger working in Netbeans 7.0.1. After completely reinstalling Ruby1.8.7/Watir2.0.1 without DevKit, click_no_wait and set_no_wait now seems to be working for me.
It means I'll have to use something else other than Netbeans to run my scripts, but at least my scripts work again. (https://github.com/oneclick/rubyinstaller/wiki/Development-Kit) I hopwe this info helps someone. GJHmf On Aug 31, 3:51 pm, GJHmf <[email protected]> wrote: > Hi all, > > I posted a few threads the other day, one of which detailed my > difficulty using set_no_wait on a validated text field; and was asked > by Jarmo Pertman whether it was in a frame. It is, and this concerns > me a little; as sadly the site I'm testing is heavily frame-centric, > with no immediate plans to modernise. > > I recently migrated from an ageing Ruby1.8.6/Watir1.6.2 test > environment to Ruby1.8.7-334/Watir2.0.1, and am now noticing more > methods that are no longer working for me in frames. For instance, > click_no_wait on a button that presents a new window works perfectly > fine in my old environment, but not in my new one. > > This is a question to the Watir developer group. Are no_wait methods > known to be failing in frames in Watuir 2.0.1? If so, are they being > addressed? If they're not, then I'll be forced to revert back to an > archiac version of Ruby and Watir. For many reasons, I don't want to > do this. > > Thanks, > > GJHmf > > (Ruby 1.8.7-334 ... Watir 2.0.1 ... XP Pro ... IE8) -- 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]
