- Support to select an element more than once (enabled by default). In order to disable this feature, use the map-based constructor of EStructuralFeatureValueProviderBase and construct the EStructuralFeature accordingly.
- Fix update of Ok button when deselecting all elements (fire second event to work around bug in DualList base class)
refs 1841

refs 1841

refs 1841

refs 1841

- Do not cache LabelValueMapping since {@link IDerivedAnnotation}s support that the {@link {EStructuralFeature} of their return value is changed at runtime
refs 1841

refs 1841

refs 1841

refs 1841

- Do not expose createComboBoxLabelValueMapping()
- Instead, provide getLabel()
refs 1841

- Implement MultiSelectionEditing support that currently supports the selection of multiple values for EReferences (based on OPAL's DualList)
- Rename ComboBoxLabelValue mapping -> LabelValueMapping
- Update AnnotationViewPartBase also on ADD_MANY / REMOVE_MANY events
refs 1841

- Add private getAnnotationValueProvider() method
refs 1841

  - Remove getEStructuralFeatureOf()
  - Expose DEFAULT_KEY (from AnnotationValueProviderBase)
  - createEditingSupport(): Pass current specification

- AnnotationEntry:
  - Remove getSpecificationElementFeature()
  - Add getSpecification(). TODO: Use this method internally in AnnotationEntry
  
- EStructuralFeatureDescriptor
  - getEStructuralFeature(): Pass current specification
  
- Base on the above, no longer base logic to compute the currently active EStructuralFeature for IDerivedAnnotiations on a temporary EStructuralFeatureDescriptor
refs 1841

refs 2171

- This should fix the related crashes that contained multiple objects with the same name
refs 1841

- Add AnnotationInstantiationMigrationProvider that augments loaded models with annotations that have been added to the AF3 installation after the creation of the model.
- Note that:
  - It is still required to use AnnotationUtils.getAnnotation() to obtain (and potentially instantiate) an annotation. This is because annotations are only instantiated for newly added model elements if the annotation view is visible.
  - IMigrationProviders that convert old attribute values into annotations cannot rely on the fact that the annotation instance already exists (since the execution order of the IMigrationProviders is not defined). Hence, the need to use AnnotationUtils.getAnnotation(modelElement, clazz, false) to obtain (and potentially instantiate) an annotation (without wrapping the model access into a command, see #2010).
refs 1841

- Prevent nested calls of selectionChanged() which could trigger a refresh of the table before all column label providers / editing support has been initialized
refs 1841

 - List<AnnotationEntry> getValues(IModelElement element) --> AnnotationEntry getAnnotationEntry(IModelElement element);
 - The semantics of the method is change to return exactly the AnnotationEntry that contains the AnnotationValueProvider-to-IAnnotatedSpecification mapping for the given model element. In the old semantics, a list of all annotation entries for model elements that had the same type as the given model element have been returned.

AnnotationEntry:
 - add isEmpty()

Consequences:
 - Fix update bug of GenericAnnotationView when deleting model elements (stale rows used to stay in the view)
 - Performance improvement

TODO: The GenericAnnotationView is still very slow during the deletion of large sub-models (and probably also during addition e.g., because of c'n'p of large sub-models) 
refs 1841

- Remove redundant dependencies (i.e., those, that are already contained and re-exported by the actual dependencies)

- Show model element name in tool tip (useful,  if name is not visible due to scrolling to the right)
refs 1841

  - Crash when setting an annotation type based filter
  - Missing updates for filters that depend on the currently selected model element
refs 1841

  - Move label provider to dedicated package
  - Move generic annotation view to dedicated package
  - Move inner classes of GenericAnnotationView to separate classes (filter support in dedicated package)
- Small documentation updates
- No functional change
refs 1841

refs 2154

- Performance optimization: Prevent reconstruction of identical column set (e.g., when only the selection or a value in the model is changed)
refs 1841

 - Cache annotation entries the different root elements. The cache for a given root element is invalidated when model elements are added to / removed from the structure beneath it.
 - Avoid superfluous updates:
   - Re-selection of a model element
   - ADD events for annotation objects. These are a caused by the addition of a model element which already triggers an ADD event.
refs 1841

Extends the Derived annotation, such that element-specfic values can be returned; Useful for aggregate annotations.
refs 2150

refs 2150

No commit message

- Fix bug that icon faking the native widget is not hidden when the actual widget is shown for editing
refs 1841

- Remove NOP override of setAnnotationValue()
refs 1841

refs 2154

- Adds support for checkboxes in the TableViewer (of the annotations). Still needs visual improvements.
- Modifies the GenericAnnotationView to support the checkbox-editing. 

- Ensure that currently selected model element is visible in table view (the change of the selection can be triggered in an external editor, e.g. the model navigator)
refs 1841,2137

- getValues(): cache AnnotationEntry list returned for given model element, significantly improving the performance of the AnnotationView for larger model. The view makes extensive use of this method from its update() method.
refs 1841

refs 1841