Limitations and Restrictions

Currently there are no methods on the event packet object for passing data down into the lower level objects used by the system. This means that if there are requirement for a pick sequence, pick type or actual pick to act differently than those defined by the currently available pick sequence methods, the developer will have to define their own object definition for the event packet in full.

It should also be noted that once an event is placed on the event stack, modifying the packet that was originally passed to the system will not change the packet that is held within the event system.

It is not possible to define an event packet, which comprises of a single specific type of pick, followed by an unspecified one of the same type of pick.

It is not possible to define an event packet that triggers a subsequent event packet off, on the completion of another, as in, does not have an "!!edgCntrl.add(<edgPacket>)" within the .close action of the first packet. As adding a new packet in the close sequence will actually stack the packet that is running, only removing it from the system once the subsequent packet has finished.