[qjackctl-devel] Re: [PATCH] New QjackCtl settings: coreaudio, freebob and netjack

[Rui N. C. <rn...@rn...>]

Rui Nuno Capela wrote:
> Stéphane Letz wrote:
>> Le 5 mai 06 à 01:34, Rui Nuno Capela a écrit :
>>
>>> Stéphane Letz wrote:
>>> ...
>>>> If you can send test screenshot of how it would be , this would
>>>> be  perfect!
>>> Here they are.
>>>
>>> Oh, and I also included yet another option, whether one can show/
>>> hide the right or left toggle button group :)
>> Really nice. Does the "small" window state is part of the global
>> state so that the small window is restored when qjackctl is launched
>> again?
>>
> 
> It better be :)
> 
>>> However, I'm still asking for some proper titling, as the complete
>>> "JACK Audio Connection Kit" one seems rather too long and fatally
>>> truncated in all of these "slim" display modes.
>> Why not:
>>
>> - JACK    (only)     ((-:
>>
>> - or Qjackctl
>>
> 
> OK. I'll stay with these two modes:
> 
> - Normal mode (all buttons shown):
> 
>   "JACK Audio Connection Kit [<preset-name>] <server-state>"
> 
> - Shrink mode (some button group hidden):
> 
>   "JACK [<preset-name>] <server-state>"
> 
> Why I do keep the <server-state> on the caption? Just because it is handy
> for it to be shown on the system-tray icon tool-tip; should not matter on
> MacOSX, I think.
> 
> 
>> Another remark i did some month ago: there is a possible pb
>> concerning starting/stopping the server. If you do the following steps:
>>
>> - launch Qjackctl
>>
>> - start Jack server
>>
>> - quit qjackctl leaving the jack server running
>>
>> - launch Qjackctl again, it sees that the server is running
>>
>> - hit the stop button in qjackctl: qjackctl is closed but the jack
>> sever is still running....  and now there is NO way for the user to
>> really stop the server.... which is bad I think. (you can do a
>> "killall jackd" of course..... ((-:  )
>>
>> You do a distinction whether qjackctl was the process starting the
>> jack server or not.... but I think this is not correct. Qjackctl
>> should allow to stop the jack server in any case. We do that in J
>> ackPilot and I think this is a more consistent behaviour.
>>
> 
> Hmm. I remember this. I guess I missed it. I thought I had some
> workaround-fix on this already. It was something about the post-shutdown
> script (Setup/Options/Scripting/Execute script after shutdown) being
> _always_ called, where you could set it as "killall jackd", at your own
> will (maybe it can be a "factory" default?).
> 
> Now I confirm that it isn't. But will be, tonight on CVS :)
> 

OK. Just made some mess into CVS [qjackctl 0.2.20.6]

- The main window buttons display is now optional. One can choose
   whether the left, right and/or transport buttons are hidden,
   making it for a total of six different modes for the main window
   presentation.

- The post-shutdown script is now also being called when using the Stop
   button, whether the jackd server has been started internally or not.
   The initial hard-coded default is now on and set to `killall jackd`.

- The most relevant transport commands (Rewind, Play and Pause) are now
   made available on the main window context popup menu.

- Closing the main window while not as an active JACK client, nor under
   a server running state, will just quit the whole application, even
   though the system-tray icon option is in effect.


Please, remember to set that "Setup/Options/Scripting/Execute script 
after shutdown" option to `killall jackd` to have this functionality 
effective immediately (unless its the first time you're running 
QjackCtl, taking the new "factory" defaults into account:).

And, of course, try the new "Setup/Misc/Buttons" options for the main 
window button hiding and what not :)

Bye now.
-- 
rncbc aka Rui Nuno Capela
rn...@rn...