Community
Participate
Working Groups
The idea is to easily be able to, from the code, find and navigate to the model element corresponding/related to the code. An idea of how to solve this is to use some kind of annotation in the code that the editor can interpret and use to open the corresponding editor. Maybe using EMF cross document reference notation, e.g. href="model.uml#//@element.3" to easily fin the correct element.
The CDT Editor integration does not contain a selection support from model to code. It used to contain a selection support from code to model, i.e. selecting an operation in the code selected the corresponding operation in the model explorer. This is currently disabled as it has caused deadlocks (there is a selection listener in the class PapyrusCDTEditor, but it is not added to the CDT widget). If you consider that this is an important issue, I may re-examine how to enable the selection from model to code and vice versa. The main problem of the latter is that the selection of an element in the model explorer changes the focus and we need to prevent model update and subsequent regeneration in this case.
I remove the target version/milestone until a new plan is decided