This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
NOTE - Engineering do not implement this until we get clearance from HIE. This is "proposal" at this point. Proposal - interactions with collapsed diagram elements should result in auto-expansion of the collapsed element 3 Use cases apply. I will open separate and make this an umbrella issue because the 3 use cases will require different engineering assignemnts and different testing. UC1 - User is traversing and selecting Navigator nodes - some of these Navigator nodes correspond to Diagram elements which are in a collapsed state. UC2 - User invokes a context menu action (or a Element tool bar action) on a collapsed Diagram element. UC3 - User is debugging a BPEL process. User is stepping through the process. User steps into a collapsed BPEL element. Setting up 3 dependent issues for this.
*** Issue 90947 has been marked as a duplicate of this issue. ***
On second thought. I am not creating separate issues. There are other use cases and it seems a bit extreme to set up separate issues for each one because we have now determined that a single fix can address all use cases - assuming that we want the same response for all use cases. The only reason to open separate issues is if we determine that there should be different responses for some use cases. However, I suggest this will be problemeatic from an implmentation point. Also, from a useabiility point, it seeems if we can be consistent it will be better anyway. - Additional use cases: UC4 - User selects an error message in the Validation output window. - User expect the corresponding node in diagram to be selected. - If corresponding node is inside collapsed container, then container should auto expand. UC5 - User is in source editor - User invokes the Go To Design action (new) - Editor switches to design view - User expect the corresponding node in diagram to be selected. - If corresponding node is inside collapsed container, then container should auto expand. In summary, these cases can be reduced to a single axium. Any action resulting in the invocation of setActiveNode on the diagram view should cause the Diagram to show the active node. If the active node is hidden because it is inside a collapsed container then the container hierarchy needs to be auto-expanded in order to allow the active node to become visible to user. Engineering - please go forward with this implementation.
Fixed for UC1, UC4, UC5, and maybe for UC3
Fixed.
Verified in Milestone 6a