Display label count

[Edgar]

Have we already switched to WXW3.02?

No not yet. There has been some exploratory work, but there is currently a lot of other stuff going on, so Audacity is officially remaining with WxWidgets 2.8 for the next release.

A lot of work was done a couple of weeks ago to make the entire Audacity code compile and run under wxWidgets3. This means that it is especially important that any new code that gets added be tested to ensure that it compiles and runs under wxWidgets3 & wxWidgets2. My previous warning was because I posted the patch while all four configurations were building but only the first two (wxWidgets3) had finished <grin-twiddling thumbs>.

[Edgar]

I have made a first tab at TrackInfoAx

I somehow feel that the description should really defined in TrackPanelAx.
[...]
The "GetDescription" method would be still helpful to display the Label counts.
[...]
By the way, NVDA is free and comes with the necessary tools to debug your patches.
[...]
I can of course perform the testing part, the latency will be terrible though.

Code: Select all

/**********************************************************************

  TrackInfo code is destined to move out of this file.
  Code should become a lot cleaner when we have sizers.

**********************************************************************/

Relying on a screen reader to read the information for the Track Info Panel from the TrackPanelAx is just asking for trouble. I suspect that is why you're getting the "interesting" results you do. If we can create a functioning TrackInfoPanelAx and cause it to read out the label counts I suspect we can also teach it to properly read out the other information. If we get that far we might be able to get Developer support to allow me to create separate TrackPanel.h/cpp, TrackInfo.h/cpp, TrackPanelAx.h/cpp, & TrackInfoAx.h/cpp files.

If we can get the GetDescription function working that I will see how to create a new function GetLabelCounts and move the functionality into that.

I once installed NVDA to do some testing with Audacity but, as I recall, it conflicted horribly with Dragon NaturallySpeaking which I use to control my computer (I'm seriously restricted in my ability to use the keyboard and to a lesser extent the mouse). I have no problem with latency – I have a good latency correction tool (a good book to read).