* library versioning is required by liblash apps
* liblash needs to be compiled with DEBUG_OUTPUT_TERMINAL
because it needs to use printf() and not lash_log()
main.c: In function 'term_handler':
main.c:54: warning: implicit declaration of function 'strsignal'
client.c: In function 'client_parse_xml':
client.c:248: warning: implicit declaration of function 'strcmp'
dbus_service.c: In function 'lashd_client_disconnect_handler':
dbus_service.c:107: warning: implicit declaration of function 'strcmp'
dbus_service.c: In function 'lash_dbus_service_connect_handler':
dbus_service.c:98: warning: implicit declaration of function 'lash_strset'
project.c: In function 'project_unload':
project.c:1131: warning: unused variable 'next2'
project.c:1131: warning: unused variable 'node2'
save_button.c:21:1: error: "_GNU_SOURCE" redefined
<command-line>: error: this is the location of the previous definition
main.c:21:1: error: "_GNU_SOURCE" redefined
<command-line>: error: this is the location of the previous definition
synth.c:8:1: error: "_GNU_SOURCE" redefined
<command-line>: error: this is the location of the previous definition
interface.c:25:1: error: "_GNU_SOURCE" redefined
<command-line>: error: this is the location of the previous definition
lash.c:21:1: error: "_GNU_SOURCE" redefined
<command-line>: error: this is the location of the previous definition
server.c: In function `server_create_new_project_name':
server.c:331: warning: incompatible implicit declaration of built-in function `strlen'
server.c:337: warning: incompatible implicit declaration of built-in function `strcpy'
* Don't try to get graph if JACK server is stopped
* Get unknown clients when JACK server start is detected
* Clear graph when JACK server stop is detected
The flag is set by lashd when a restoring client makes first contact. This
commit ends the short-lived appearance of the long-as-f*** environment
variable LASH_CLIENT_IS_BEING_RESTORED.
(Added value: lash_client_is_being_restored() actually works now!)
This function allows the client to query whether it was started by lashd
for the purpose of restoring it as part of a project. It does so by checking
if the env var named LASH_CLIENT_IS_BEING_RESTORED is set to the client's PID.
So far only the basic stuff works, save for LASH_Client_Remove commands
for which support hasn't been implemented in lashd yet. Also, the internal
logic of lash_shell needs a closer look.
- When a task commences always send Progress signal with value 0.
- When a task finishes always send Progress signal with value 100.
- Never send Progress signal of 0 or 100 during a task's lifetime.
In the past these signals weren't behaving consistently for Save and Load tasks.
Also, a Progress signal with value 0 signified both the beginning and end of a
task, leaving it up to the controller application to decipher which is which.
This is now fixed and apps can rely on 0 meaning 'go' and 100 meaning 'done'.
Nedko Arnaudov
Juuso Alasuutari