[LAU] qjackctl gets confused when used through ssh -X

[Jörn Nettingsmeier]

Rui Nuno Capela wrote:
> On Sun, 01 Nov 2009 17:29:37 -1000, david <gnome at hawaii.rr.com> wrote:
>> Rui Nuno Capela wrote:
>>> drew Roberts wrote:
>>>> On Sunday 01 November 2009 08:26:59 fons at 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
> confusion.
> 
> eats precious screen real estate, which is already bloated.

agreed. still, it would be cool to save qjackctl state explicitly, not
just on exit. i've been hit by this a number of times already. scenario
is this:

you are testing some bleeding-edge jack checkout on a brand-new,
pre-alpha rt kernel patch with highly demanding clients. every two
minutes, jack goes down in flames, often taking qjackctl with it (or
vice versa). the settings are not saved. on the next testing iteration,
stuff magically works (or ceases to work), because the settings are not
what you think they are.

since it only bites when you're testing, i've never got around to
reporting explicit state save as a feature request, but now i've learned
i'm not alone, i will :-D

rui, how about saving state whenever the "OK" button in the setup dialog
is pressed?