2 Nov
2009
2 Nov
'09
3:13 p.m.
Rui Nuno Capela wrote:
On Sun, 01 Nov 2009 17:29:37 -1000, david
<gnome(a)hawaii.rr.com> wrote:
confusion.
eats precious screen real estate, which is already bloated.
if you take a closer look, for quite some time (since ever?) the "Preset
Name:" label, the preset name edit-box and the "Save" and
"Delete" buttons
are all on the same line and in this sequence, an usual pattern for preset
management (found on all of my apps, btw:) and if you hover the mouse on
the "Save" button the tool-tip balloon will tell you that it "Save
settings
as current preset name".
ain't that enough?
Is enough for me. Just was mentioning a thought since it seemed like
some people were confused about just what the Save button was saving ...
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Rui Nuno Capela wrote:
> drew Roberts wrote:
>> On Sunday 01 November 2009 08:26:59 fons(a)kokkinizita.net wrote:
>>>> again, that's nothing to do
>>>> with the wrong place of the qjackctl configuration file but _when_
the
>>>> changes are committed to it: at
program exit.
>>> So why then is there a 'Save' button at all ?
> the "save" button is to save current settings and only those as a named
> preset.
>
> those settings are the ones seen in that particular page
> (Setup/Settings), being the ones strictly related to jackd arguments.
>
> the "save" is about creating/updating a named preset. it is _not_ to
> save nor commit the program configuration state to disk. still that
only
occurs on
program exit.
So call it "Save As A Preset". Sounds like it might reduce
user