8 Jan
2010
8 Jan
'10
5:57 p.m.
Rui Nuno Capela <rncbc(a)rncbc.org> writes:
On Fri, 8 Jan 2010 09:35:01 +0000, Chris Cannam
wrote:
good question. i'll add another one:
hacking a SIGUSR1 handler is dead-easy, i know, but... how one application
gets to know which filename to load/save its state from/to in the context
of ladish level 1 session ?
Use the current filename. If there is no current filename do what you
think is better, either show save as dialog or ignore the signal. Other
possibility is to allow supply of non-existent file path to be used for
first save in the app. Better make it non-default behaviour because it
is somewhat strange if you dont use ladish. I.e. user usually expects
start to fail if project file supplied at commandline does not exist.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
On Mon, Jan 4, 2010 at 12:03 PM, rosea
grammostola wrote:
> "When ladish studio is being saved, applications that are run at level
1
receive
the SIGUSR1 UNIX signal.
How does an application indicate that it intends to "run at level 1"?