Skip to content

Open classifier information view from more places #2439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lwrage opened this issue Sep 15, 2020 · 1 comment · Fixed by #2492
Closed

Open classifier information view from more places #2439

lwrage opened this issue Sep 15, 2020 · 1 comment · Fixed by #2492
Assignees
Milestone

Comments

@lwrage
Copy link
Contributor

lwrage commented Sep 15, 2020

Summary

The classifier information view can only be opened from the outline view when the classifier is selected. There are more places where the classifier can be determined from the selection. It should be possible to open the classifier with such a selection.

Expected and Current Behavior

It should be possible to open the classifier information view when

  • a classifier is selected in the navigator
  • an element referencing a classifier is selected in the navigator or outline view
  • a component instance is selected in the navigator, outline view, or instance editor
  • an element referencing a component instance is selected
  • from the text editor

There should be a keyboard shortcut for this.

Environment

  • OSATE Version: 2.8.0
  • Operating System: Win10
@keh181
Copy link
Contributor

keh181 commented Oct 30, 2020

The Open Classifier Information view now supports the following from the Outline and AADL Navigator Views:

  • Alt+C shortcut for Windows/Linux and Option+C for MacOS
  • Prototypes and Subcomponents open referenced classifier if there is one, otherwise opens classifier that it is a part of
  • Parameters, Data Ports, Feature Groups, and Access now show related classifier if one is provided

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants