| From "David Bailes" <
drbailes@...>
| Wed, 14 May 2008 11:28:33 +0100
| Subject: [Audacity-devel] String Freeze
> On Tue, May 13, 2008 at 7:00 PM, Gale Andrews <
gale@...> wrote:
> >
> > Re: getting all the Edit menu access keys working, by renaming two of
> > the menu items I can see a way of getting those for Silence and Select...
> > working without setting that for Select... to "."
> >
> > I'm suggesting "&Silence" is renamed to "Silence Audi&o" and "Disj&oin"
> > renamed to "Detac&h at Silences" (also in the Labeled Regions sub-menu).
> > This then lets us use "&Select...".
>
> I think that disjoin can be most consistently viewed as yet another
> variant of split, so would be better renamed "split at silences".
> Doesn't help with access keys, though. Not sure it's helpful to
> introduce another verb, detach, when split is used for all the other
> cases.
Hi David
"Split at Silences" is quite good, but we already use a different word
(Disjoin) for breaking up a track into different clips at silences.
Disjoin is rather different to "Split" because Split AFIK can only
produce two or three individual clips, whereas Disjoin has no limit
to the number of clips it can produce. Given "Detach" or "Detach at
Silences" lets us fix the access key problem, I think on balance it's
better, unless you have another solution other than "Split at
Silences (&h)" which I would rather not do.
> > A David pointed out, using ellipses "..." in front of a cascading menu
> > is non-standard on Windows. I'm therefore proposing to take the
> > opportunity to remove all of these cascading menu instances, unless
> > they should be in because of normal behaviour on the other OS'es?
>
> If you're going to change these, then you also remove the ellipsis
> from the following menu items:
> edit->preferences
> help->about audacity
> help->show welcome message
> help->Index
> help->audio device info
>
> An ellipsis indicates that further info is needed before a command can
> be executed, and in these cases there is no command, they simply open
> a dialog box.
I understand that's a good summary of Microsoft recommendations,
but it's still I think debatable and open to interpretation, looking at
the Windows programs I have. For example some have the ellipses
after Help > About and some don't, though all open a dialog box.
If I look at Firefox's Help menu, Help > About Mozilla Firefox has
no ellipses - you get a dialog to read but you do still have to choose
"Credits" or "OK", so action is still needed in that sense. OTOH Help >
Report Web Forgery which goes to a web page is ellipsed. Microsoft
Front Page is similarly ambivalent in the Help menu, having ellipses
before "Customer Feedback Options" though it is not a program
command. I can see the logic of these distinctions, though they are
not following strict MS recommendations?
Other programs omit ellipses only 1) where the menu item is a direct
command like "Cut" which requires no further input whatsoever, or
2) in front of cascading menus. This is Audacity's approach except
that it extends it to use in front of cascading menus as well. I've
always found this use in front of cascading menus confusing and do
think they should be removed in this case, unless most programs on
Mac and Linux do this.
I had a quick look for screenshots with menu drop-downs and only
found Safari (Mac version, Debug menu) which had no ellipses at all?
Sorry, I don't know. Leland?
So if there's no further input, I figure I will remove ellipses from
in front of cascading menus, but not anywhere else.
Gale
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
