[linux-audio-dev] LASH and LASH_Terminal client flag problem
drobilla at connect.carleton.ca
Wed Nov 23 00:41:35 EST 2005
On Tue, 2005-22-11 at 20:20 +0100, Florian Schmidt wrote:
> On Tue, 22 Nov 2005 20:01:05 +0100
> Florian Schmidt <mista.tapas at gmx.net> wrote:
> > I ardour i try to hack around this by stripping "offending" commandline
> > options from argv before passing it to lash_init..
> Actually this doesn't work right.
> > so the docs should at least point out the problem
> This remains though :) So basically apps who save state to files should
> ignore state files specified on the commandline when in LASH mode,
> except for those apps that are unable to change the state file selection
> lateron upon user demand (i.e. little terminal helper tools, that don't
> have a GUI or other means to load a different state file).
If it's specified on the command line, why save it as a key and/or file?
Pick one. :)
I can put something in the docs, but it's a bit obvious and/or app
dependant. Ignoring some command line arguments is an acceptable
solution, but so is ignoring the configure key and/or file.
More information about the linux-audio-dev