It's not for lack of wanting to. We've already done a few custom apps
that attempt to retrieve field names dynamically when Window-Eyes is
unable to do so natively, and it's a fun challenge. Unfortunately, my
resources are currently tied up in other projects. But, I will put it on
our list.
Aaron
On 3/2/2012 3:03 PM, martin webster wrote:
Hi Aaron,
You could write this in your sleep where as i would have to really
work on it. come on mate sort it out. Come out of retirement.
warm regards.
Martin webster.
--- On *Fri, 3/2/12, Aaron Smith /<[email protected]>/* wrote:
From: Aaron Smith <[email protected]>
Subject: Re: request for a script to read goldwave standard
control interface
To: [email protected]
Date: Friday, March 2, 2012, 7:34 PM
On 3/2/2012 12:38 PM, Dave Bahr wrote:
go to the control properties with f 11, then to the visual tab,
then click where it says, time and status visual, and make that
use the Tone Meter setting. Then there will be a button labeled
status properties. If you go into there, there is an example of
what I'm talking about.
Thanks. That's was exactly what I was looking for.
When you tab to the edit box, mine just reads, negative 20.00. No
information as to what the field containing the number is for.
If you listen carefully, you'll actually hear that Window-Eyes is
providing a field name, but it is incorrect. For the first
control, the label is 10, because the closest text to the edit box
is 10.00%, right below it. The same goes for all of those edit
boxes. So they do have field labels, but they are wrong. So one
could hook the OnChildFieldName event for the Tone Meter and, when
and edit box gets focus, do what you said you had to do manually:
To get that info, I have to route the pointer and press the mouse
up key.
While it would be more time consuming and challenging to develop a
custom field name solution for every dialog in the entire app,
this particular window would be easy enough to do, because the
field labels that you really want are all pretty much in the same
location in relation to the edit box controls.
As to vst plugins, one reason I like the fact that goldwave
supports them, even in beta, is that the interface you can use is
either the vst interface from the actual plugin, or a "basic"
interface that goldwave maps onto the plugin. It's my hope that
the basic interface can be accessible, not the vst one. You are
right Aaron in the accessability of vst plugins, lots are gui.
Do does this basic interface work? How do I get to it?
Does that clear anything up at all? Or did I just make it more
confusing and repeat myself too much?
That was much better.
Thanks!
Aaron
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
