Constraints

Due to limitations of PlantUML used for image output, there is a limit to the number of data points that can be represented in the [Timing Diagram] view. If the display settings are at their default values, some data will not be displayed in the [Timing Diagram] view if you create 80 or more [Timing] models.
This constraint can be avoided by reducing the size of the image output by PlantUML. The specific methods are as follows:
From the [Timing Diagram] Inspector of the [Timing Model], reduce the zoom level of the [Timing Diagram].
From the [Timing Diagram] Inspector of the [Timing Model], increase the unit of the tick marks in the [Timing Diagram].
From the [Timing Diagram] Inspector of the [Timing Model], decrease the width of the tick marks in the [Timing Diagram].
If you set reserved words from PlantUML in the fields of each model (lifeline, transition, etc.), they may be misinterpreted, resulting in incorrect timing diagrams or error messages.
For example, setting a hyphen (-) in the name of each model will display error messages. Please use an underscore (_) instead.
The [Timing Table] view does not support transposing rows and columns.
The display contents of the [Timing Table] view and the [Timing Diagram] inspector may not be immediately reflected when editing other views. Switching to a different view and then redisplaying it will reflect the changes.
Even if you add your own class that inherits a metamodel class that can be added with this package, the [Timing Table] view and [Timing Diagram] view will not be available.
You can add the [Timing Table] view definition to classes other than timing models from the context menus and ribbons of various navigators, but please do not use this feature as it is a reserved function.