Which causes slow startup (minutes and minutes with decent number of charts) and huge amount of events sent with thousands of charts. This means downtime when xJog is restarted.
Saw that charts table state column does indeed keep those events in actions array so they are executed again and again and again, but could not quite figure out a good way around this.
Should we remove those manually after they are executed? Or is there a reason not to do that. How to prevent them ending up there in the first place so they are not processed after a restart.
Seems reasonable to put them there on state transition as otherwise they might get lost if xJog is unexpectedly closed, but it does also seem reasonable to remove them after they are executed the first time. Or should we avoid entry-exit events in states where charts are for a long time, especially final states.
No proposal yet, just a description of a problem so far.
Which causes slow startup (minutes and minutes with decent number of charts) and huge amount of events sent with thousands of charts. This means downtime when xJog is restarted.
Saw that
chartstablestatecolumn does indeed keep those events inactionsarray so they are executed again and again and again, but could not quite figure out a good way around this. Should we remove those manually after they are executed? Or is there a reason not to do that. How to prevent them ending up there in the first place so they are not processed after a restart.Seems reasonable to put them there on state transition as otherwise they might get lost if xJog is unexpectedly closed, but it does also seem reasonable to remove them after they are executed the first time. Or should we avoid entry-exit events in states where charts are for a long time, especially final states.
No proposal yet, just a description of a problem so far.