Page 1 of 2

Suggestion

Posted: Mon Aug 24, 2015 2:31 pm
by jack magee
I would like to suggest there should be a button on the GUI for the Shift+A Stop and set cursor function http://manual.audacityteam.org/o/man/tr ... u.html#set

Thanks Steve for pointing me to that option

Re: Suggestion

Posted: Mon Aug 24, 2015 3:16 pm
by Gale Andrews
Thanks I'll count your "vote" for that. But it probably won't happen in the default button set, as some are opposed to any extra buttons.

Gale

Re: Suggestion

Posted: Tue Aug 25, 2015 10:23 pm
by jack magee
Gale Andrews wrote:Thanks I'll count your "vote" for that. But it probably won't happen in the default button set, as some are opposed to any extra buttons.

Gale
I think if an extra button cannot be added it is sad. Can the people opposed not ignore it.? Audacity has great potential but some things are too awkward

Re: Suggestion

Posted: Tue Aug 25, 2015 11:22 pm
by steve
jack magee wrote:I think if an extra button cannot be added it is sad. Can the people opposed not ignore it.? Audacity has great potential but some things are too awkward
I think that other ways to tackle the "awkwardness" are being considered that do not require adding another button.

There would be advantages for Audacity to run a sound stream continuously, rather than creating a new sound stream each time you play or record.
A consequence of Audacity doing this would be that "Pause" would be the same as "Stop and place cursor".
So effectively you have two "stop" states: one where playback/recording stops and the cursor "rewinds" back to where it started, and the other "stop" state would leave the cursor in its new position.
An additional benefit of this approach is that both types of "stop" allow editing (currently you can't edit while "Paused").

Re: Suggestion

Posted: Wed Aug 26, 2015 9:55 am
by Gale Andrews
steve wrote:
jack magee wrote:I think if an extra button cannot be added it is sad. Can the people opposed not ignore it.? Audacity has great potential but some things are too awkward
I think that other ways to tackle the "awkwardness" are being considered that do not require adding another button.

There would be advantages for Audacity to run a sound stream continuously, rather than creating a new sound stream each time you play or record.
That would be much better, but we still have those who want an extra button for Loop Play, and the changes you describe may not happen soon.

So I still favour allowing customisation of Transport Toolbar for extra buttons and completely flexible button order.

Gale

Re: Suggestion

Posted: Wed Aug 26, 2015 10:01 am
by waxcylinder
Gale Andrews wrote:So I still favour allowing customisation of Transport Toolbar for extra buttons and completely flexible button order.
Gale, do I assume that by "customization" you mean the ability to remove and add buttons in the toolbar?

If so, then I would support such a proposal - not least because one of the things I really dislike currently is the way some buttons change when the modifier keys Shift and Ctrl are held down (often not appropriate to the particular task in hand).

Peter.

Re: Suggestion

Posted: Wed Aug 26, 2015 10:06 am
by jack magee
Gale Andrews wrote:
steve wrote:
jack magee wrote:I think if an extra button cannot be added it is sad. Can the people opposed not ignore it.? Audacity has great potential but some things are too awkward
I think that other ways to tackle the "awkwardness" are being considered that do not require adding another button.

There would be advantages for Audacity to run a sound stream continuously, rather than creating a new sound stream each time you play or record.
That would be much better, but we still have those who want an extra button for Loop Play, and the changes you describe may not happen soon.

So I still favour allowing customisation of Transport Toolbar for extra buttons and completely flexible button order.

Gale
Agree. Thanks for feedback guys

Re: Suggestion

Posted: Wed Aug 26, 2015 10:08 am
by waxcylinder
jack magee wrote:I would like to suggest there should be a button on the GUI for the Shift+A Stop and set cursor function http://manual.audacityteam.org/o/man/tr ... u.html#set
Jack,

my interim workaround while this and other proposals for dealing with the same issue is to replace the existing shortcut Shift+A, which I always found awkward so seldom used, with a single keystroke shortcut.

The one I chose for myself is the NUMPAD_INSERT key (on my numpad it's a double-size key). All you have to ensure with that key is that the NUM_LOCK is not "on" (don't ask me how I know ... :oops: )

For how to make alterations or additions to shortcut assignments see this page in the Manual: http://manual.audacityteam.org/o/man/ke ... ences.html

WC

Re: Suggestion

Posted: Wed Aug 26, 2015 10:46 am
by Gale Andrews
waxcylinder wrote:
Gale Andrews wrote:So I still favour allowing customisation of Transport Toolbar for extra buttons and completely flexible button order.
Gale, do I assume that by "customization" you mean the ability to remove and add buttons in the toolbar?
Yes. Ideally I would see it that you would open a customize dialogue that makes Transport Toolbar editable. You can then add buttons to the toolbar by dragging buttons from the customize dialogue to the toolbar, and remove buttons by dragging them to the customize dialogue. You could also drag any button on the toolbar into a different order.

I don't know if Widgets can handle that on all three platforms.

If not then I support having more pre-ordained alternative transport toolbars to choose from in Interface Preferences.
waxcylinder wrote:One of the things I really dislike currently is the way some buttons change when the modifier keys Shift and Ctrl are held down (often not appropriate to the particular task in hand).
I agree but at least one developer thinks that modifier keys changing buttons should be retained because it makes actions more discoverable. Few apps that I know do that. I would just rip it out as confusing and ugly if I had my way. ;)


Gale

Re: Suggestion

Posted: Wed Aug 26, 2015 11:33 am
by waxcylinder
Gale Andrews wrote:
waxcylinder wrote:One of the things I really dislike currently is the way some buttons change when the modifier keys Shift and Ctrl are held down (often not appropriate to the particular task in hand).
I agree but at least one developer thinks that modifier keys changing buttons should be retained because it makes actions more discoverable. Few apps that I know do that. I would just rip it out as confusing and ugly if I had my way. ;)
+1 to "rip it out as confusing and ugly"

It certainly is both of those :evil:

And re-purposing buttons like that is bad GUI design IMNSVHO :ugeek:

Peter.