What is the benefit of parsing an event rather than handling them
directly?
I need to be able to update a stack/card script in a standalone, and I
cannot because of the limit imposed. The stack script contains (mostly)
typical handlers (i.e. openStack, resumeStack, etc.) for handling messages
What is the benefit of parsing an event rather than handling them
directly?
I need to be able to update a stack/card script in a standalone, and I
cannot because of the limit imposed. The stack script contains (mostly)
typical handlers (i.e. openStack, resumeStack, etc.) for handling messages
RCS wrote:
What is the benefit of parsing an event rather than handling them
directly?
I need to be able to update a stack/card script in a standalone, and I
cannot because of the limit imposed.
Actually, you can't because of OS restrictions in Win and UNIX which prevent
a running EXE from
Hello,
I need to be able to update a stack/card script
in a standalone, and I cannot because of the
limit imposed ...
Hummm .. Seems easy enough to me. Integrate one or
more do statement[s] in your generic handler. The
script that gets 'done' can be located elsewhere, e.g.
in a field, in a
