pala
January 23rd, 2003, 05:34 PM
Hi
I'm using Girder now for a few weeks, and first all a big applause to Ron.
It's a great tool.
Yet I bumped into this problem: Although the startup guide tells the
contrary, it seems that in case a single event is linked to various
commands each command get launch one after the other.
Yet I have to groups: one enable, one disabled. On an event
which get caught in the first group, I disable the first group an enable the second. Yet if I do that then the same event is caught by another command in the second group!
I solved this by setting a timer to make the switch of groups. IE the event
set the timer, the timer get the switch. There it work. But this looks like
an ugly patch.
I just thought that I could try to put the two group in the opposite order,
which might look better, but wouldn't if I have to go back to first situation.
Anyone has a clean solution for this.
BTW: its not a repeated event, I set repetition timers. Putting waits here
and there doesn't help also.
Waiting for your ideas.
If its not possible maybe there should be some "flush all events" command. (suggestion for Ron) ... Or maybe patch the manual... well
I know you'd rather change ten page of code than ten lines of Documentation :)
See ya all
Daniel
I'm using Girder now for a few weeks, and first all a big applause to Ron.
It's a great tool.
Yet I bumped into this problem: Although the startup guide tells the
contrary, it seems that in case a single event is linked to various
commands each command get launch one after the other.
Yet I have to groups: one enable, one disabled. On an event
which get caught in the first group, I disable the first group an enable the second. Yet if I do that then the same event is caught by another command in the second group!
I solved this by setting a timer to make the switch of groups. IE the event
set the timer, the timer get the switch. There it work. But this looks like
an ugly patch.
I just thought that I could try to put the two group in the opposite order,
which might look better, but wouldn't if I have to go back to first situation.
Anyone has a clean solution for this.
BTW: its not a repeated event, I set repetition timers. Putting waits here
and there doesn't help also.
Waiting for your ideas.
If its not possible maybe there should be some "flush all events" command. (suggestion for Ron) ... Or maybe patch the manual... well
I know you'd rather change ten page of code than ten lines of Documentation :)
See ya all
Daniel