refs 2229

- Ensure that in each session, the hint how to create new connections is displayed until the user has managed to create three of them.
- (Side note): The current implementation cannot distinguish connections created interactively by the user, and connections created by a model-transformations. However, we can assume that a user who is able to issue a model-transformation also knows how to create a channel in the GUI.
refs 2229

refs 2126

refs 2126

- Ignore update of IDs that may be triggered massively when saving a model that contains a lot of generated artifacts for which IDs are typically not assigned.
- Disabling the delivery of notifications during the assignment of IDs is not possible since the kernel needs to be notified about ID changes.	
refs 2309

- Prefer the potentially a bit less efficient but safer Display.getDefault.syncExec() over Display.getDefault.asyncExec() to avoid NPEs triggered by model modifications
refs 2323

- Ensure that UI updates triggered from EMF notification mechanism are executed in the UI context (using Display.getDefault.asyncExec())
refs 2323

 - In case the label could not be found, return a string representation of the value. This is useful to implement custom label providers for model elements are edited in combo boxes.
 - Prevent potential NPE

- Add IAnnotationValueProvider.isHidden() that allows to hide annotations from any view (useful for internal attributes that should not be exposed to the user). Default = false
- Extend AnnotationEntry and AnnotationFilter accordingly

- GSNPositionedEditPartBase*: Avoid code duplication by pushing refreshDecorationFigure() to PositionedEditPartBase
- PositionedEditPartBase.refreshDecorationFigure()
  - Avoid SWT Image leak by reusing the same icons
  - Add more null-checks to implementation
- MarkerViewPart -> column updater: Avoid SWT Image leak by disposing old image before setting a new one

- Keep order of elements to be selected (e.g., EENum values) etc. by using a LinkedHashMap instead of a TreeMap

Adds the possibility to filter the list of available choices for an enum-type annotation via the annotation's value provider.
Therefore, a map containing the class of the to be filtered model elements and the allowed enum literal must be given in the constructor of the value provider.

refs 2226

refs 2289

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

refs 2255

Bugfix: Use annotation instance key in setValue(). This is already done in getValue() / getLabel()

- Add Id, version, and ConQAT tags to XML files

* Mainly documentation cleanup
* Remove some commented out code

org.fortiss.tooling.kernel.internal.storage.eclipse.ModelContext:
org.fortiss.tooling.kernel.utils.EMFResourceUtils:
 - Resolve B.19 issue (numbering scheme as of Aug. 14, <https://af3-developer.fortiss.org/projects/autofocus3/wiki/Check-list_for_Code_Reviews/56>) "Use static imports"
refs 2255

- Annotations are now instantiated in ElementCompositorService. Hence, this migration will not be required in the future.
refs 2208

- Ensure that the annotation view is updated when switching between multiple projects by fixing a bug in the EAdapter registration
refs 2236

- Fix last commit: Actually allow one connection from a IHierarchicElement (node) to a free IConnector
refs 2233

- Prevent multiple fan-in for IHierarchicElement -> IConnector connections (was erroneously enabled in some cases)
- If this is desired, concrete compositors should override canConnectInterally()
refs 2233

- Instead, ensure that DiagramEditorBase has the focus when a child edit part is added or removed
- This works around #2207 and also the same part of #1491 as with the old workaround
- Summing up:
   - Undo/redo of operations on the model only works if either the NavigatorViewPart or a DiagramEditorBase has the focus
   - This makes sense if the active view provides editable items itself (e.g., the GenericAnnotationView) *and* provides undo/redo (currently not the case for GenericAnnotationView).
   - For other (read-only) view (e.g., Model Markers), this behavior is confusing for the user
refs 2207,1491

- Move annotation value service, annotation value provider base classes and annotation extension point to org.foritss.tooling.base
- Remove createEditingSupport() from IAnnotationValueProviderBase and move functionality to org.fortiss.tooling.base.ui.annotation.editingsupport.EditingSupportFactory instead
- Rename extension point to org.fortiss.tooling.base.annotation.

Example binding:

<extension point="org.fortiss.tooling.base.annotation">
  <annotation binding="org.fortiss.af3.timing.annotation.valueprovider.CIValueProvider">
     <modelElementClass modelElementClass="org.fortiss.af3.component.model.Component"/>
  </annotation>
</extension
- Adapt all known users of annotation framework to new structure
- The change is a preparation to fix #2208, i.e. to put the instantiation of a model element and its annotations into a single undo/redo command
refs 2208

- Avoid case distinction in GenericAnnotationView that handles construction of EditingSupport for boolean annotations
- This fixes the bug that the EditingSupport was only created correctly for derived annoations (#2225)
- Add TODO to delegate construction of label provider to annotation value provider, too (#2226)
refs 2225,2226

- Fix crash in some annotation value providers during undo/redo by checking if annotation specifications are registered with a model element
refs 2204

refs 2133

- If the annotations view is not visible (i.e., not opened at all, or not the active tab), create and raise the properties view
- Otherwise, just create the properties view, but do not raise it (the annotation view acts as a replacement for many properties)
refs 2133