Thread: [Audacity-devel] A few more to add to the list
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Leland <aud...@ho...> - 2006-06-30 03:55:37
|
On the Mac, if you float the meter toolbar you get side by side meters as expected, but if you resize it even by 1 pixel, it will jump to over and under meters. This does not happen on Windows. Droplists in toolbars and SelectionBar are not keyboard accessible. (I could swear they were once...prolly wrong though.) There's track selection issue that's been a little difficult to pin down... Start a new project and create some silence. Now bring up the Effect menu and you can see that the effects are available. Don't select one but dismiss the menu and click anywhere within the trackpanel background. Nothing will appear to happen, but go back to the Effect menu. The are no longer available. Another thing that has happened as long as I can remember is that every so often, you'll get a stray vertical broken line that runs across a track. Can't figure out a pattern yet. Leland |
From: Leland <aud...@ho...> - 2006-06-30 05:45:12
|
On 6/29/06 10:55 PM, "Leland" <aud...@ho...> wrote: > Droplists in toolbars and SelectionBar are not keyboard accessible. (I > could swear they were once...prolly wrong though.) > I've figured out what this is, but the "fix" will irritate mousers to no end. So, I think I'm finally gonna have to bite the bullet and add an "Enable accessibility features" option to preferences. Question is should I make a new preferences pages and move the other 2 accessibility related options to the new page or should I just add them to a separate group on the Interface page? Leland |
From: Markus M. <me...@me...> - 2006-06-30 08:14:00
|
Leland schrieb: > I've figured out what this is, but the "fix" will irritate mousers to no > end. So, I think I'm finally gonna have to bite the bullet and add an > "Enable accessibility features" option to preferences. > Leland, please re-consider if this is really necessary. Markus |
From: James C. <cr...@in...> - 2006-06-30 11:50:49
|
Markus Meyer wrote: > Leland schrieb: >>I've figured out what this is, but the "fix" will irritate mousers to no >>end. So, I think I'm finally gonna have to bite the bullet and add an >>"Enable accessibility features" option to preferences. > Leland, > please re-consider if this is really necessary. What is it about making the drop down accesible that would irritate mousers? I would hope we can make it so that accesibility is always enabled and is neutral or benficial to other users. Keyboard navigation is generally good for power users. It's hard to see it causing a problem for mousers. --James |
From: Leland <aud...@ho...> - 2006-06-30 13:09:57
|
On 6/30/06 6:55 AM, "James Crook" <cr...@in...> wrote: > Markus Meyer wrote: >> Leland schrieb: > >>> I've figured out what this is, but the "fix" will irritate mousers to no >>> end. So, I think I'm finally gonna have to bite the bullet and add an >>> "Enable accessibility features" option to preferences. > >> Leland, > >> please re-consider if this is really necessary. > > > What is it about making the drop down accesible that would irritate mousers? > > I would hope we can make it so that accesibility is always enabled and > is neutral or benficial to other users. Keyboard navigation is > generally good for power users. It's hard to see it causing a problem > for mousers. > The problem only happens if there are tracks within the project. An empty project doesn't exhibit the problem. What's going on is that you aren't able to change the wxChoices using the keyboard if there are active tracks. The up and down key events are handled by the CommandManager as if they were destined for the TrackPanel. So the wxChoices never see them. The "fix" is actually very easy and that's to add TrackPanelHasFocus to the flags for all (or most) of the trackpanel related keystrokes to ensure they are not hijacked as they are now. Why this will irritate mousers if this flag is set is that when they click on any of the wxChoices within the toolbars or the selectionbar, the focus will be set to the control on which they clicked. Then attempting to use the keyboard to do something within the trackpanel will not work as it no longer has the focus and the user will have to click "something" within the trackpanel to give it focus. Btw, this doesn't happen on the Mac...don't know about Linux (I'm reinstalling that tonight) and it only seems to be a concern for wxChoices. WxComboBoxs do not have this problem. How about I make the change (a one liner for now) and let everyone see if it will be an irritant? Leland |
From: James C. <cr...@in...> - 2006-06-30 11:50:46
|
Great. I would like to do a consolidated list in a few days time. Markus - What is the situation on Bugzilla bugs? I had a look recently and some open ones seemed not to be problems on current HEAD. --James. Leland wrote: > On the Mac, if you float the meter toolbar you get side by side meters as > expected, but if you resize it even by 1 pixel, it will jump to over and > under meters. This does not happen on Windows. > Droplists in toolbars and SelectionBar are not keyboard accessible. (I > could swear they were once...prolly wrong though.) > There's track selection issue that's been a little difficult to pin down... > Start a new project and create some silence. Now bring up the Effect menu > and you can see that the effects are available. Don't select one but > dismiss the menu and click anywhere within the trackpanel background. > Nothing will appear to happen, but go back to the Effect menu. The are no > longer available. > Another thing that has happened as long as I can remember is that every so > often, you'll get a stray vertical broken line that runs across a track. > Can't figure out a pattern yet. Yes, I've seen that too, and I have some idea what it is about. > Leland |