Eclipse eTrice merge requestshttps://gitlab.eclipse.org/eclipse/etrice/etrice/-/merge_requests2023-08-31T08:14:28Zhttps://gitlab.eclipse.org/eclipse/etrice/etrice/-/merge_requests/53Resolve "Inconsistent transition target handling in behavior diagram layout"2023-08-31T08:14:28ZEyrak Paen-RochlitzResolve "Inconsistent transition target handling in behavior diagram layout"Closes #86Closes #86Release 5.0.0https://gitlab.eclipse.org/eclipse/etrice/etrice/-/merge_requests/16[ui, generator.doc] qualified diagram export paths by model namespace2023-08-31T08:28:00ZEyrak Paen-Rochlitz[ui, generator.doc] qualified diagram export paths by model namespaceDiagram export filepaths are now prefixed with the containing model
namespace to avoid name collisions.
Issue #50
Closes #50Diagram export filepaths are now prefixed with the containing model
namespace to avoid name collisions.
Issue #50
Closes #50Release 4.0.0Eyrak Paen-RochlitzEyrak Paen-Rochlitzhttps://gitlab.eclipse.org/eclipse/etrice/etrice/-/merge_requests/15[core.room] fix binding validation to check inherited external end ports2023-08-31T09:03:22ZEyrak Paen-Rochlitz[core.room] fix binding validation to check inherited external end portsIssue 46 is partly an awkward interaction between the diagram editor behavior and the core room xtext services. The diagram editor uses the xtext validator directly on combinations of EObjects that would normally not be possible in an xt...Issue 46 is partly an awkward interaction between the diagram editor behavior and the core room xtext services. The diagram editor uses the xtext validator directly on combinations of EObjects that would normally not be possible in an xtext document (due to scope provider constraints). This means that the validator has to account for cases that are outside the possible xtext scope.
Not sure if this should be refactored in some way, or if it's worth it?
Commit message:
Validation for connection of external end ports now also accounts for
inherited ports. Note that due to current scope provider behavior, it is
not actually possible in the textual editor to encounter this case.
HOWEVER, it does become an issue in the diagram editor, because it
currently uses ValidationUtil on arbitrary ports in the diagram without
consulting the scope.
Issue #46
Closes #46Release 3.2.4Eyrak Paen-RochlitzEyrak Paen-Rochlitzhttps://gitlab.eclipse.org/eclipse/etrice/etrice/-/merge_requests/14Resolve "include_images option is missing from doc gen launcher config tab"2023-08-31T09:03:43ZEyrak Paen-RochlitzResolve "include_images option is missing from doc gen launcher config tab"Closes #47Closes #47Release 3.2.4Eyrak Paen-RochlitzEyrak Paen-Rochlitzhttps://gitlab.eclipse.org/eclipse/etrice/etrice/-/merge_requests/12[ui.structure] Simplify inheriting actor positioning2023-08-31T09:03:04ZChristian Hilden[ui.structure] Simplify inheriting actor positioning- Inherited actor diagrams always take the layout of the base diagram
- On open/update, diagram will be resized to base diagram size if
smaller than base diagram
- No scaling of base actor elements will be done during resize/layout
Clos...- Inherited actor diagrams always take the layout of the base diagram
- On open/update, diagram will be resized to base diagram size if
smaller than base diagram
- No scaling of base actor elements will be done during resize/layout
Closes #29Release 3.2.4Eyrak Paen-RochlitzEyrak Paen-Rochlitz