| Summary: | [Properties] When an element is selected it shall be interpreted as Global Selection | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Tristan Faure <faure.tristan> |
| Component: | Core | Assignee: | Camille Letavernier <cletavernier> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | jacques.seronievivien, toni.siljamaki |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Tristan Faure
Contributing it to the global selection is probably not a good idea, as the property view itself depends on the current selection. This seems dangerous... And we don't have a lot of control on the Property View itself, as we're relying on the Tabbed Property View Framework (We cannot really prevent the view from being refreshed on selection, for example...) However, there are (or will soon be) a few mechanisms to implement the behavior you are describing: - The "Comments" tab should be implemented with the new property view framework, which should allow to edit the parameter's comments through the "Edit" button in the Operation's property view (This button actually opens the parameter's property view in a Dialog) - There is a widget which implements a MultiReferenceEditor, with an embedded property view on the right pane (Something similar to the Stereotype's editor in the Profile tab). It could be used for operation/parameters (List of parameters in the left pane, and parameters' properties in the right pane). This widget is already used for editing Opaque Expressions, for example. Should this bug be closed? OK to close it I close this task |