You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current behavior is implemented in the klighd framework and it is not really a bug but intended this way.
The basic UX concept is that the editor defines the context for the diagram view. If the selection of a diagram element that is defined in a different resource would jump to the textual source, it would switch to the respective editor and display the diagram for that editor, losing the previous context.
I think this behavior would be annoying because it happens rather often that you select elements without the intent to look at the source code, e.g. to navigate in the model, highlight them for presentation, or expand them.
I could try to add an alternative action, e.g. ctrl+click, to navigate to the source code of reactors in other files. This way, losing context would be intentional but still inconsistent with the default.
@lhstrh I agree, if we want this behavior, we should add a new ticket because this will take some careful consideration in order to provide a pleasant user experience.
Alt+Click on a diagram element will now jump to the associated code
section even if it is located in a different editor.
This implementation only affects the Epoch IDE.
The current behavior is implemented in the klighd framework and it is not really a bug but intended this way.
The basic UX concept is that the editor defines the context for the diagram view. If the selection of a diagram element that is defined in a different resource would jump to the textual source, it would switch to the respective editor and display the diagram for that editor, losing the previous context.
I think this behavior would be annoying because it happens rather often that you select elements without the intent to look at the source code, e.g. to navigate in the model, highlight them for presentation, or expand them.
I could try to add an alternative action, e.g. ctrl+click, to navigate to the source code of reactors in other files. This way, losing context would be intentional but still inconsistent with the default.
@lhstrh I agree, if we want this behavior, we should add a new ticket because this will take some careful consideration in order to provide a pleasant user experience.
Originally posted by @a-sr in #341 (comment)
The text was updated successfully, but these errors were encountered: