Doug, you're right, I ended up, in my fieldName event handler, causing window eyes to invoke a summary command, and so ...
I don't remember quite how I did it, it's just that I didn't realize at the time that the 2 were related; so, I thought I'd mention it. the other reason I get hard hangs, when closing an app, seems to be due to an intermitant problem introduced in 7.1. when changing window focus, window eyes will rarely just hang. it seems to happen most often if I'm changing back to the script manager; but in any case, having a window close, and so another is activated, or doing it myself with alt-tab, will sometimes cause this problem. Chip ------------------------------ Chip Orange Database Administrator Florida Public Service Commission chip.ora...@psc.state.fl.us (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 Lee [mailto:doug....@ssbbartgroup.com] > Sent: Saturday, August 15, 2009 9:35 PM > To: gw-scripting@gwmicro.com > Subject: Re: Tracking down a hang-on-exit issue in an app script > > My FieldName and FieldSummary don't call each other, but logically > it would make sense to me for FieldSummary to call FieldName and/or > FieldData. I'm not sure how you're saying you got an infinite loop > though. Were your FieldName and FieldSummary functions calling > each other, or are you saying your FieldName somehow caused > Window-Eyes > to issue a FieldSummary call, and Window-Eyes itself completed the > circuit by calling your FieldName again from there? That would be > interesting, as I don't know a way to have a script cause WE to > request field name/data/summary on demand, except by making sure the > focused window's type is right and then simulating an OnObjectFocus > event. That's a pretty hefty thing to do from a FieldName > function. :) > > On Sat, Aug 15, 2009 at 09:10:31PM -0400, Chip Orange wrote: > Hi Doug, > > I had a script which hooked these same events, and it was > hanging on me at > one time. the problem was that the summary event calls the > fieldName event, > but I didn't know it at the time, and could end up in an > infinite loop. I'm > mentioning it just in case you aren't aware of this relationship. > > Chip > > > -----Original Message----- > From: Doug Lee [mailto:doug....@ssbbartgroup.com] > Sent: Wednesday, August 12, 2009 10:11 PM > To: gw-scripting@gwmicro.com > Subject: Tracking down a hang-on-exit issue in an app script > > I've had an app script hang hard twice on app close (out of > many many script > reloads and a fair number of actual app shutdowns without > incident). When > it happens, the machine becomes sluggish, there's no speech, > and the only > solution I've found is to shut down Window-Eyes via the Task > Manager (my > method being Ctrl-Shift-Esc, hope the correct tab is active, > type "wineyes" > but not too fast or too slow, type Alt-E, pause, type Alt-E > again, pause, > press Space, wait for the dust to settle). > > The script hooks OnObjectFocus, OnChildFieldName/Data and > OnChildSummary > from the Desktop window (but each has code to avoid doing anything if > window.process.processID <> > clientInformation.applicationProcess.processID), > and OnStateChange for the shared objects. The hangs only > occur rarely and > always when I shut down the application. > > I'm assuming this is some sort of script loop, but that's > hard to prove. > > Any suggestions as to where to look first? > > > -- > Doug Lee, Senior Accessibility Programmer SSB BART Group - > Accessibility-on-Demand mailto:doug....@ssbbartgroup.com > http://www.ssbbartgroup.com "While they were saying among > themselves it > cannot be done, it was done." --Helen Keller > > -- > Doug Lee, Senior Accessibility Programmer > SSB BART Group - Accessibility-on-Demand > mailto:doug....@ssbbartgroup.com http://www.ssbbartgroup.com > "While they were saying among themselves it cannot be done, > it was done." --Helen Keller >
