Sequence Local - DMS - February 2003 - by Bob Le Gob


Overview:
*********
The Sequence Local module triggers a chain of actions.
The events triggering the chain of actions are triggered
on client side.


Editor:
*******
- Length: Enter the length of your sequence (number of 
          “output” events of the module instance).


Implementation:
***************
Actions:
- start            (S) : Starts the module on the client
- destroy          (S) : Destroys the module on the client
- inputOneByOne    (C) : Each time this action is activated, 
                         it triggers a out'n' event, starting
                         from out1, then out2, then ..., then
                         out'length', then out1 again.
- inputAllAtOnce   (C) : When this action is activated, all
                         events from out1 to out'length' are
                         triggered one after the other.
                         This doesn't impact the inputOneByOne
                         action current status.
Events:
- entering         (S) : Client is being started
- destroyed        (S) : Client is being destroyed
- ended            (S) : Client ended
- out'n'           (C) : Output n triggered


Notes regarding Sequence 3.1 module:
************************************
- In Sequence module, all out'n' events are triggered on server side.
- As the module is only running on server side, this require 
constant client/server communications, be it useful or not.
- If you trigger the events all at once, linked client actions
will be run only on the client who triggered the events.
- If you trigger the events one by one and link them to client
actions, these actions will occur on the clients who triggered
the events. For example, if a client triggers out1, he will get
the action linked to out1, but if another client then triggers
out2, this other client will get the action linked to out2. The
first client doesn't get the second action, and the second client
doesn't get the first one.


Notes regarding Sequence Local 1.0 module:
******************************************
- All out'n' events are triggered on client side.
- Client/server communications are used only if needed.
- Triggering the events all at once will run client actions on
the client as in Sequence module but will not require network
communication.
- Triggering the events one by one is now handled for each client
separately. Each one thus triggers its own chain of actions step
by step.