| commit | cb73db0fa09e15a1c879566c7fe0d830c20115af | [log] [tgz] |
|---|---|---|
| author | Paul D'Pong <sdamrong@redhat.com> | Tue Jun 16 09:28:00 2020 -0400 |
| committer | Sravan Kumar Lakkimsetti <sravankumarl@in.ibm.com> | Wed Jun 24 10:06:15 2020 -0400 |
| tree | 20c1e8c276e623f939712a4afe68b46f30915d99 | |
| parent | 1fc69ddba25b47146cdb8291c85a1e0e62dc16dc [diff] |
Bug 564097 - [GTK][HiDPI] Cairo auto scaling causing scaling problems Removed unused scaling factor variable & gsettingsProc in Device. Applied dpi_changed signal to all shells created, allowing Eclipse to detect when zoom has changed & relayout. Before the signal was connected only to the first shell of a Display. (I'm guessing that Eclipse runs more than one shell and the first shell actually never changes monitors -> never changes DPI when user moves the Workbench to a higher DPI monitor) On DpiChanged signal emitted, deviceZoom is actually changed to the correct value rather than the scale factor of the point (0, 0). On first shell creation, get the scale factor on the monitor the shell is created on. This ensures that the icons/images are scaled properly. Change-Id: I9a554cf605ce8e5d96fdcc31f355a242b5511975 Signed-off-by: Paul D'Pong <sdamrong@redhat.com>
Thanks for your interest in this project.
See the following description for how to contribute a feature or a bug fix to SWT.
Information regarding source code management, builds, coding standards, and more and be found under the following link.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Contact the project developers via the project's “dev” list.
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!