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

[Christian Damus <give.a.damus@xxxxxxxxx>]

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