Re: [mdt-papyrus.dev] Highest-priority provider in State Machine blocks

[Ansgar Radermacher <ansgar.radermacher@xxxxxx>]

Hi Christian,

the CustomUMLEditPartProvider has always been at the highest priority (well, at least for the last 4 and a half years, when plugin names have been re-factored). Thus, I think that there is no real reason behind this setting, though we will certainly have to test the diagram well after your proposed change.

Best regards

Ansgar

On 01/06/2016 18:35, Christian Damus wrote:

Hi, Team,

Why does the State Machine Diagram define its custom edit-part provider at highest priority?

   <extension point="org.eclipse.gmf.runtime.diagram.ui.editpartProviders" id="ep-provider">

      <editpartProvider class="org.eclipse.papyrus.uml.diagram.statemachine.custom.providers.CustomUMLEditPartProvider">

         <Priority name="Highest”/>

          …

      </editpartProvider>

   </extension>

This makes it impossible for applications like Papyrus-RT that are building on Papyrus to customize the behaviour of this diagram in their context.  The base implementation of a diagram should always use lowest priority.

What would happen if I knocked this down to lowest priority before Neon RC4 (after deleting the other edit-provider that the diagram doesn’t need)?

Thanks,

Christian

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

-- 
Ansgar Radermacher                CEA/DRT/DILS/LISE
http://www-list.cea.fr/index.htm
phone: +33 16908 3812
mailto: ansgar.radermacher@xxxxxx