Fons Adriaensen writes:
> On Thu, Oct 16, 2008 at 11:40:09AM +0300, Nedko Arnaudov wrote:
IMHO this should be provided by libjack API itself.
This is same thing that kfoltman requested these days, to be able to
check whether app is started as part of process of restoring lash
session. I'm fine with this and such approach in general.
> Looking at the source, there's indeed a lot of
I have plan to allow user to tweak commandline of both lash first time
launched apps (when launched through lash control app) and restored lash
app processes, before launched. However this is not in my short term
> If there is any data in there that is essential
Unless you have app that has no internal state at all. Examples:
fluidjack and jkmeter (ver nice app btw). This simplifies lash
integration for simple commandline apps.
> The only exception would be things that are essential
Can you give some example, please?
> So it seems it would be a better approach to let
Such option seems fine. I'm only opposed to *requiring* such
app<->liblash interaction, because it will make commandline argument
management more tricky.
> This issue (and some others, like jack connections)
I think the easiest option would be to store internal state in lash and
ignore commandline when restored as part of lash session. Other option
would be to declare such behaviour to lash, either by call of liblash,
or in the desktop entry for your app (X-LASH-XXX fields, we have some of
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----