Community
Participate
Working Groups
When the DiagnosticView gets an update, it does an "expand all" on its tree. This has two problems: - profiling a private client application shows that as much as 25% of the time taken in changing row selection in a table control is attributed to expand-all in this view because the validation service validates every selection - in my private client application, I have a "collapse all" button in the view's toolbar. It's irritating to a user who uses this to collapse the diagnostic view tree that changing the selection in a table expands everything again Either the DiagnosticView should just not expand all when it is updated with validation changes, or it should provide some API that lets clients customize this behaviour.
New Gerrit change created: https://git.eclipse.org/r/149344
Gerrit change https://git.eclipse.org/r/149344 was merged to [develop]. Commit: http://git.eclipse.org/c/emfclient/org.eclipse.emf.ecp.core.git/commit/?id=60bf8c5eab441c207b468e91f0f1d951b6d26e64
(In reply to Eclipse Genie from comment #2) > Gerrit change https://git.eclipse.org/r/149344 was merged to [develop].
Fixpublished in the 1230_201909261922 build.
should this be marked with "test"?
## TESTING INFORMATION ### Summary of the critical part of the change The default implementation of the DiagnosticView expanded all nodes which led to performance issues. ### Potential regressions Regression may occur in UI applications that previously assumed or required that the diagnostic view is expanded.
