I still can't get this to work yet. Though I have come across another
problem with it when running a test from Python.
The 3rd windows displayed (should only be standard html), is
Also, the controls on the window I launch it from become disabled so I
have no option but to close down the application.
Something very strange is going on here as it works Ok when I run the
complete application within Windmill and use the Windmill IDE to click
the button to launch the window.
Is this something to do with the Windmill-Python Interface possibly?
On Aug 17, 10:33 pm, Adam Christian <adam.christ...@gmail.com
> This should work, however sometimes the timing causes the code to not
> re-inject that stuff.
> Before you do the action that opens the new window you should call:
> 'overrideDialogs', which will inject the new window.open code.
> The best way to check that the window registered is by using firebug in the
> IDE and looking at windmill.windowReg.
> However with a couple of my use cases I have seen it continue to switch back
> to the previous window, which looks like a bug somewhere in the
> windmill.testWin() function. If you see that same behavior you can log a
> github bug and I will further investigate this.
> On Tue, Aug 17, 2010 at 9:58 AM, sophiedmr <
> > Running from python, I successfully log on and a new window comes up.
> > I call
> > client.setWindowByTitle(title=u'fastrac')
> > in my test and control passes to the new window with no problem.
> > I then click a button on this 2nd page which launches another window
> > but when I try to call
> > client.setWindowByTitle again with the 3rd page title it doesn't pass
> > the test control to this third window.
> > Any ideas?
> > Thankyou,
> > Sophie
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Windmill Developers" group.
> > To post to this group, send email to windmi...@googlegroups.com
> > To unsubscribe from this group, send email to
> > windmill-dev...@googlegroups.com
> > .