Page History
...
| Event Type | Description |
|---|---|
| Relative time events using a literal expression | See for example the first transition in the above state chart. The time expression consist of a comma-separated list, like for example 2 days, 12 hours. The list elements or tokens consist of numbers and units. Allowed units are second, minute, hour and day. Units can be given in singular or plural form. Thus, 3 seconds, 1 minute is allowed. Furthermore, all units are case insensitive. Seconds can be specified as non-negative floats. All other units must be specified as positive integers. In order to tell the model compiler that the time expression defines a relative time duration, set the Is Relative flag to true. If this is not done, the compile will print a warning. |
| Relative time events using dynamic expressions | See for example the second transition in the above state chart. Return type of the expression must be Integer. Unit of measure is seconds. This is sensible for short timeouts, e.g. 30 seconds. Again, the Is Relative flag must be set to true. |
| Absolute time events using dynamic expressions | See for example the third transition in the above state chart. The return type of the expression must be DateTime. This is sensible for time events best calculated dynamically. For instance, an event triggering the transition in three years. |
| Noteinfo | ||
|---|---|---|
| ||
The prefix after or at is added by MagicDraw automatically for relative respectively absolute time triggers. You only need to add the time expression in the time event specification dialog. |
...
Overview
Content Tools