| commit | bbfcd587130dc0d166e5b7d0ab454c9519fbfa5d | [log] [tgz] |
|---|---|---|
| author | Michael Keppler <Michael.Keppler@gmx.de> | Sun Jul 23 19:47:04 2017 +0200 |
| committer | Lars Vogel <Lars.Vogel@vogella.com> | Sun Oct 22 18:56:17 2017 +0200 |
| tree | 7b1be622a77062cc5e5a4fa416b2efcf7eba53c7 | |
| parent | 6a4b7123160757f0ccfa1587bc166eccd85e0081 [diff] |
Bug 520069 - Better performance when setting viewer filters Suppress updating item labels when filters of a viewer are updated, since updating the filters will not modify any of the existing labels. This can reduce the refresh() time drastically. The change in AbstractTreeViewer seems to be an independent bug, which was only uncovered by this change. If labelRefreshing is disabled, the association between viewer elements and widgets will get out of sync, but that execution path was probably not exploited up to now. Change-Id: Ic94999d9bcba49a94d2157b2e50cc411e4f9c850 Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de>
Thanks for your interest in this project.
Platform UI provides the basic building blocks for user interfaces built with Eclipse. Some of these form the Eclipse Rich Client Platform (RCP) and can be used for arbitrary rich client applications, while others are specific to the Eclipse IDE. The Platform UI codebase is built on top of the Eclipse Standard Widget Toolkit (SWT), which is developed as an independent project.
Website: http://www.eclipse.org/platform/ui/
For more information, refer to the [Platform UI wiki page] 1.
Contributions to Platform UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the [Platform UI - How to contribute wiki page] 2 page on the team wiki.
You need Maven 3.3.1 installed. After this you can run the build via the following command:
mvn clean verify -Pbuild-individual-bundles
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.