commit | 44192018fe7ef1cbbd3bf91c0ba88b52367f52cb | [log] [tgz] |
---|---|---|
author | Rolf Theunissen <rolf.theunissen@gmail.com> | Sat Aug 29 16:11:49 2020 +0200 |
committer | Rolf Theunissen <rolf.theunissen@gmail.com> | Sat Aug 29 16:11:49 2020 +0200 |
tree | ccbbc3229044e75000550560a0dea07abd232f5d | |
parent | 8d3e5c315412dc590d84149f4e50e8b3e062c066 [diff] |
Bug 566375 - Disappearing 'View Menu' toolbar button in History view - Part 2 Forcing the UI update of the topright had has side effect that the toolbar is not rendered at the correct location. When first updating the toolbar and then forcing the UI update, the toolbar is correctly renderer. The forced UI update causes another flicker of the toolbar. This is prevented by disabling redraw while repositioning the toolbar. Change-Id: Iaceb41965f787f554139779300f7da11455c32f2 Signed-off-by: Rolf Theunissen <rolf.theunissen@gmail.com>
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.
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 page on the team wiki.
Several test plug-ins have a dependency to the Mockito and Hamcrest libraries. Please install them from the Orbit Download page]3:
Currently the following plug-ins are required:
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.