refs 2779

  - Get the number of moved (sub-)elements and store it in the extended metadata map of the moved elements.
  - Adjust the movement point calculation to the number of elements (als improve snap to grid).
refs 2751

refs 2358

- Copy operation are not dirtying the model any more: Add a write flag to annotation actions; Only those will are dirtying a model now.
- Context menu in the annotation view is no longer visible for non-editable annotations.
- References and multi-references are now correctly handled:
  - Correct the set logic.
  - Offer two kinds of pastes for multi-reference annotations: append, replace.
- Fix duplicated context menu entries for the SafetyIntegrityLevel annotation (details: see bug report).
refs 2361

- Move the getEStructuralFeatureDescriptor method to the IAnnotationValueProvider interface.
- Move the getContectMenuEntries method for AnnotationValueProviders to the ValueProviderBase class.
  - Remove the DefaultAnnotationContextActions interface that provided a default implementation.
  - Add copy & paste Actions to the ValueProviderBase class.
- Improve the handling of (Annotation) instanceKeys in the GenericAnnotationView.
- Generalize the Action to create random values for the annotations of the visible element set in the annotation view:
  - Can handle only Number types up to now.
  - Add a static method in AnnotationUtils that allows to provide this capability in AnnotationValueProviders.
- Add a BaseMathUtils utility class in org.fortiss.tooling.base to handle "dynamic" Number conversions that are not considered in Apache common's MathUtils: Used, e.g., for the randowm number generation.
- Update the EnergyConsumption- & WcetValueProviders.
refs 2361

refs 2347

refs 2347

refs 2444

Fixed invalid propositions from guards.
refs 2220

refs 2349

refs 2346

refs 2358

 - Triggers
   - F2 hotkey
   - context menu
 - Effects:
   - Raise properties view,
   - Puts focus on "name" field
   - Select all previous contents of "name" field
refs 2355

refs 2750

refs 2653

refs 2646

refs 2646

- This will be performed by the IElementCompositorService that is called from createNewSourceDropContext().
- Doing it here already, will trigger an expensive check for duplicate IDs when the ID assignment is issued for the second time from the IElementCompositorService
refs 2759

- I.e., do this for each specification instead of the "contained" model element. Since
"contained" might already have an any, this would trigger an expensive algorithm to
check if there are duplicated IDs.
refs 2759

- getReferencingResourceURIs(): Load side-car model resources via ResourceSet.getResource. This has the advantage that custom resource factories will be considered

- Performed some refactoring (no functional change) and added documentation
refs 2709

refs 2709

refs 2729

- prepareAnnotationEntry(): Comment out warning in case the annotation has not been instantiated yet. In the current situation, it has a performance impact on model transformations.
refs 2228

- prepareAnnotationEntry(): Emit a warning in case the annotation has not been instantiated yet. The goal is to remove the code that instantiates the annotation on the fly in the long run.
refs 2228

refs 2728

refs 2727

refs 2727

refs 2727

refs 2726

refs 2726

refs 2726

refs 2726

Ensure that IDs have been assigned to all new model elements before they are hooked to the project / resource
- Rationale
  - Model elements for which no ID has been assigned, have id 0 (which is the default value). 
  - When the new element is hooked to the resource, ResourceUtils.KernelResourceFactory.KernelXMIResource.getId() is called, which internally calls setId() to synchronize the XMI ID with the AF3 ID. In case the ID is still 0, this implicit call will corrupt the ID -> model object map (by override the mapping for key 0).
- Changes
  - ElementCompositorService: Assign IDs *before* hooking new element to the container (but of course using the container to determine the next free ID)
  - ModelElementCompositorBase: Assign IDs to newly instantiated annotations