Doug, How about working your way down through the control window's accessible object? I seem to remember there's eventually a value field, which you should be able to set, and which shouldn't effect the state of the control on the screen?
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: Monday, August 10, 2009 2:34 PM > To: gw-scripting@gwmicro.com > Subject: Re: Best place to set control properties for speech? > > Ah yes, I forgot to mention that setting control.checked does not work > here; it won't take. I think this means that setting control.checked > is actually meant to check the on-screen control. I want to tell WE > when the screen control is checked, not change the screen control's > state. > > On Mon, Aug 10, 2009 at 02:26:06PM -0400, Chip Orange wrote: > Hi Doug, > > there is a control object, which is returned by the control method of > the window object, which you can use to effect a lot of the things > mentioned. here's some sample documentation for the checkbox type of > control: > > Navigation: > The Window-Eyes Object Model > > > Objects > > > Control > > > Control Types > > > CheckBox > > > Properties > > > Checked > Previous page > Return to chapter overview > Next page > Sets or returns a > CheckState > enum used to specify the checked state of a check box. > Syntax > Retrieving > long_value = object.Checked > where object is a > CheckBox > object. > Setting > object.Checked = long_value > where object is a > CheckBox > object. > > > > > > > ------------------------------ > > 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: Monday, August 10, 2009 2:14 PM > > To: gw-scripting@gwmicro.com > > Subject: Best place to set control properties for speech? > > > > I want to set a control's attributes (or properties or whatever we > > want to call them), like name, type, state, and value, in a way that > > makes the settings get used by Window-Eyes, so for example, WE > > will correctly honor user settings for what is said for Summary and > > other commands. > > > > I use the OnChildFieldName/Data events for a field's name and value, > > and for window type, I set window.type before WE tries to > announce the > > field. > > > > But I'm not sure where to set control state. Example: Is there > > somewhere I can set a checkbox state so that the Summary command, > > tabbing into a field, etc. will speak the state correctly? > > > > This issue may also apply to position data such as "1 of 5," but I > > haven't had to mess with that yet. > > > > I know Speak is an option, but I think of it as a last > resort: It can > > break user option honoring, require its own localization effort, and > > requires one to know all the places to put new code so the > user won't > > notice inconsistencies. > > > > > > -- > > 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 >
