Martin Robillard

The current implementation is purely stateless, which less to a complex and inefficient design. With the recent refactoring (#466) it should be possible to implement the rendering of the sequence...

This is extra code to maintain and diagrams can be ported by using a previous version of JetUML if need be.

**Description** Attempting to create a sequence diagram where a call to a constructor is followed to a call to the same object after a call to another object leads to...

This is a one line change in `EditorFrame`: ```java public EditorFrame(Stage pMainStage, Optional pOpenWith) { ... TabPane tabPane = new TabPane(); tabPane.setTabDragPolicy(TabPane.TabDragPolicy.REORDER); ``` **Update:** Unfortunately this JavaFX feature [is buggy](https://bugs.openjdk.org/browse/JDK-8295064)....

**Description** The boundaries of nodes can jump around when some of their text properties are edited. This is caused by the value of `FontMetrics#getDimension` being inconsistent, namely, it returns different...

**Description** Depending on hardware, a large diagram size (set through `View | Set Diagram Size`) makes it look like nothing happens when a user attempts to create a new diagram...

Currently, the position of the nodes is snapped to the grid, but their dimensions (width and height) are not.  It might be interesting to find a way to snap...

#182 Supply Javadoc comments for MatcherAssert

3

#182 Supply Javadoc comments for all methods of `MatcherAssert`.

The information should be accessible via renderers, and the object state lifecycle will become much simplified

Retire the control flow class and replace it with the same services offered via the `SequenceDiagramRenderer`.