Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Bug 421383 - Graphics Scaling issues on high DPI displays

Revision as of 06:30, 19 December 2014 by Sravankumarl.in.ibm.com (Talk | contribs) (New Api changes)

Capture the the design discussion for the Bug 421383

New Api changes

The following api needs to modified

Point Device.getDpi() - This api is currently used by printing functionality this will be extended to displays so that it return pixels per inch in each direction. this will be added to Monitor class as well.

Additional changes in Monitor class a new attribute Point dpi will be added to Monitor class and getDPI() will return this attribute. this will be calculated per Monitor and held in this object


Image class modifications.

The image data is held through NSimage in Cocoa, Image handle in Windows, pixmap resource in GTK+2 and Cairo surface for GTK+3. Now this particular structure needs to modified to hold multiple entries. so these will be held in an array so that these image representations could be held. Currently we are planning for images for 3 dpi values 100%, 150% and 200% The image selection will be according to the following table. This calculated based on the 100% correspond to 96 in Windows and Linux and 72 for Mac [1]
Cite error: <ref> tags exist, but no <references/> tag was found

Copyright © Eclipse Foundation, Inc. All Rights Reserved.