Thanks for your comments Bob!
Bob Ham [EMAIL PROTECTED] writes:
On Thu, 2008-10-16 at 00:10 +0200, Fons Adriaensen wrote:
2. lash_extract_args()
The type of main()'s argv is char *argv[], so
why is the second argument a triple pointer ?
Re-arranging the elements of argv does not
require
Emanuel Rumpf [EMAIL PROTECTED] writes:
Hi
Hello Emanuel
I get handler/signal doesn't exist messages.
If I press the save button in lash_panel:
lash_control_signal_handler: Received unknown signal 'ProjectSaved'
lash_control_signal_handler: Received unknown signal
Hi
I get handler/signal doesn't exist messages.
If I press the save button in lash_panel:
lash_control_signal_handler: Received unknown signal 'ProjectSaved'
lash_control_signal_handler: Received unknown signal
'ProjectModifiedStatusChanged'
Is that expected behavior ?
(lash 6.0rc1, Compiled
On Thu, Oct 16, 2008 at 11:40:09AM +0300, Nedko Arnaudov wrote:
The trend is to remove usage of argv at all. As for documentation, I
agree LASH needs better one. In current documentation (somewhat out of
date), argv thing is supposed to be opaque. I.e. LASH app should not
know what lash
Some questions and comments regarding the LASH release candidate.
1. lahs_init()
Would it be possible to document the contents of
the first argument 'lash_args_t *args' ?
I'd be happy to give lash all the info it needs
but feel quite strongly that I should be able
to provide this myself and not
