Doug, If you wouldn't mind running the focusControl script, it would tell me whether the error is restricted to my system or not.
You would do something similar, except that after setting focus to some control (not the list view) manually, just use the focusControl script to try and set the focus to the list view control. I only have xp where I am now, and it is not experiencing the problem. If you don't see the problem using focus control, then I'll work more with it, and possible vista windows explorer configurations, until I can isolate it. the problem for example scripts is that the 2 which are failing are many hundreds of lines long, and it will take some time to extract a working example, while testing with the focusControl should only take less than 5 minutes. thanks. Chip ------------------------------ Chip Orange Database Administrator Florida Public Service Commission [email protected] (850) 413-6314 (Any opinions expressed are solely those of the author and do not necessarily reflect those of the Florida Public Service Commission.) > -----Original Message----- > From: Doug Geoffray [mailto:[email protected]] > Sent: Tuesday, June 30, 2009 8:42 AM > To: [email protected] > Subject: Re: problem with setting focus in 7.1 > > Again, to add to this, since the original problem was reported with > Windows Explorer under Vista, I brought up Windows Explorer > in Vista and > the immed window. I move the physical mouse over the treeview on the > left of the Explorer window and put focus in Immed (both are > visible). > I then issued the following line in Immed: > > mouse.window.activate : mouse.window.focus > > And this didn't work. Then I remembered I can only activate overlap > windows so I then did: > > mouse.window.overlap.activate : mouse.window.focus > > And Windows Explorer took activation and the treeview took > focus as it > should. I then put the mouse over the listview, brought up Immed and > issued the same line and again, Windows Explorer took > activation and the > listview took focus. > > So my best guess is activation wasn't set correctly before > setting the > focus. At this point I don't see any problem with Window-Eyes itself. > > Doug > > Aaron Smith wrote: > > On 6/29/2009 9:32 PM, Chip Orange wrote: > >> I was pointing out it's not just my script, it's someone else's > >> script as > >> well. that makes it no longer an issue which may be a > coding mistake; > > > > I disagree. Coding errors aren't restricted to individuals. > Besides, > > I'm not able to duplicate any focus issues using Immed, or my own > > scripts. For example, if I bring up the Run dialog, then bring up > > Immed, then do: > > > > @for each x in ActiveWindow.Children : x.Focus : Sleep 1000 : Next > > > > This successfully puts activation in the run dialog, and > focused each > > control, pausing one second between focuses. > > > > I can also use Virtual View in the Run dialog to focus any of the > > buttons. > > > > So now I have two scripts that do work, and you have two > scripts that > > don't work. This is why we need an example of the code that's not > > working. Otherwise, we're just guessing what the problem might be. > > Unlike Doug, I'm more apt to point fingers at the code than at > > Window-Eyes. <grin> > > > > Aaron > > > > > > -- > Doug Geoffray > GW Micro, Inc. > Voice 260-489-3671 > Fax 260-489-2608 > http://www.gwmicro.com > >
