What is the reasoning behind creating an Application Event to use for a transition as opposed to having a transition generate an event by ticking the "Generate Event for this transition"?
An example is GoToDm2Request in the DM2 state machine.
Application Events vs System Events
- jpurdum
- Enovation Controls Development
- Posts: 153
- Joined: Mon Jun 21, 2010 11:19 am
Re: Application Events vs System Events
On that particular example (GoToDm2Request), no good reason. I think it may have been inherited from a 2.0 config or even earlier before the generate option was widely used. This actually was not an application event, it was one that was just created, which you would do by going to the events list and adding an event.
Usually, you uncheck the box to create a transition on an existing event, such as a key stroke on a screen that's already tied to an event, and you want that same key stroke to cause more than one transition between states in one or more state machines. Or in the case of an actual application event such as a NvMgr.done from the NvMgr (Database manager) application.
Usually, you uncheck the box to create a transition on an existing event, such as a key stroke on a screen that's already tied to an event, and you want that same key stroke to cause more than one transition between states in one or more state machines. Or in the case of an actual application event such as a NvMgr.done from the NvMgr (Database manager) application.