[nvda] Re: Audacity problem

Hello,
What audacity guys are doing or perhaps it's the toolkit they are using problem, as a name they are exposing words such as "radioButton", "staticText", "statusLine"... ETC. When any particular controll gets focused it is possible to retrieve it's text by sending a "getWindowText" winapi message. With object navigation and insert+b you can get roles and states spoken at this point. 

Peter


Gene  wrote:
The odd thing is that if you are in the Audacity window and use insert b, the screen is read and text is read. I don't know if this is what you were getting at in your last message. Object navigation certainly does not produce useful information. I'm not using the latest snapshot so I don't know if this might change marginally but, at least with my nontechnical background, it strikes me as odd that NVDA can identify the buttons and read the associated text in the main window as well as other structures including the cursor position when using insert b but can't read anything useful otherwise. 

Gene
----- Original Message ----- From: "Peter Vágner" <peter.v@xxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx>
Sent: Wednesday, September 26, 2007 12:47 PM
Subject: [nvda] Re: Audacity problem



Hello,

James Teh  wrote:
The problem is that these applications don't expose information about some of these controls through MSAA or some other accessibility API. In these cases, we can try to access the information through some other API (perhaps some standard Windows API for that type of control or an API specific to a custom control). For example, as Peter noted, some of these controls might expose their information as window text or the like.
I was wrong when I was tallking about values in my last email on this subject. In fact we are interested in window name not a value in case of radio buttons and checkboxes. So I found a way how to retrieve these names but this only works when controls are focused using caret navigation. When object navigation is used audacity returns some strange values and I am afraid we can do nothing about it. For example we are not able to read status bar, and all the static texts. A bit of code I was about to commit is now there so when new snapshots is made you may play with it if you feel like. for anyone who knows audacity it may be almost usable. For the others I am very sorry. 

Peter
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: 
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda



To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: 
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda


To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open 
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda

Other related posts: