I’m creating a new macro for Safari to resize & center the front window on my iMac 27" Retina display.
I started with a simple test, just setting the window size:
Resize Front Window to Pixels
To: 500 horizontally, 1000 vertically
When I measure a resized window with the PixelStick app, it’s 1000 x 2000 pixels. (PixelStick’s ruler corresponds to numbers of Retina pixels.)
Before I go ahead and double the dimensions in KM macros, I’d like a more complete understanding of the relation of KM screen positions and dimensions on both Retina and standard displays.
Thanks @JMichaelTX for alerting Peter and updating the KM Wiki.
The Wiki pages currently say, “So a retina screen will have half as many points as pixels.”
At least once in the Wiki, I’d say something more explitict like, “On a standard resolution display, one point is the same as one pixel; on a Retina display, one point is two pixels.”
It’s customary for page layout apps (like Pages and InDesign) to specify text size & ruler dimensions in Points. In this realm, documents are rendered on devices with widely varying resolutions, from computer monitors to smartphones to hi-res color printers. So it’s essential to have a measuring unit that’s not based on pixels.
You could follow the model of Pages and InDesign by leaving “points” out of action names, field labels, etc. Instead, simply add a “pt” suffix to value fields.