It's not difficult to define events, I prefer to divide events into different classes, like the following:
(1) Compound Messages.
Code Id: CAPE_EventMsg_Compound.
Subclass message Id list:
1- One of the compounds changes it's name, please care here just one compound changes it's name. Then UO receives this event, and compares old compound list with new compound list, to check which one compound's name changed, it's very easy. If multi compounds changed their name, should send out this event once when each compound name changed.
2- Remove one of the compounds. Similiar with compound rename.
3- Add one new compound.
(2) Run Control Messages.
Code Id: CAPE_EventMsg_RunCtrol.
Subclass message Id list:
1. Return to initial status, clear all cache datas.
2. Return to initial status, but still use all cache datas.
2. Input value changed after a successful calculation.
(3) Reaction Messages.
Code Id: CAPE_EventMsg_Reaction.
Subclass message Id list;
1. One of the reactions changed it's name.
2. Remove one of the reactions.
3. Add a new reaction.
4. One of the reactions adds/removes a kinetic equation.
And so on.Statistics: Posted by bcbooo — 02 March 2016, 03:14
]]>