To work around this, many of the tools can use the keyboard for precise positioning.
#Xscope colors wrong full
The short version is that the mouse movement is only reported in full screen points (two pixels on a Retina display.) Effectively, that means you can only point at every other pixel. For the gory details about what's wrong, there's this Radar bug report. Unfortunately, Apple hasn't made mouse movement as precise as the display yet. Each tick on the ruler is two pixels wide and the position indicator reports the exact pixel location (you'll probably want to turn on the Loupe so you can see the pixel you're pointing at!) Even pixels will always be on the top or left of the two pixel line, while odd pixels are on the bottom or right.Īs you use xScope, you'll find some things are incredibly hard to do with the mouse. If you need some help getting used to this convention, try displaying the Ruler and turning on the position indicators.
Similarly, the width and height of a frame is displayed at the right and bottom edge of the two pixel line. For example, a horizontal guide positioned at 123 pixels will show the 123rd pixel on the top edge of the guide. The question is then which pixel of those two being displayed is the right one? xScope always measures a single pixel at the top or left edge of the two pixel line. A good example of this are the Guides and Frames. It's really hard to see a single Retina pixel, so two are used instead. There are many cases where xScope reports a single pixel value, but displays two pixels for the measurement. It also allows consistent edge snapping (using the Control key while dragging) and the ability to do screenshots at full Retina resolution. This also applies to everything else that relies on what is displayed on screen.Īt first, it may be confusing to see xScope report screen locations that aren't on the physical display, but it's handy to have a Loupe that can view and check graphics before they're scaled. In the example above, the Loupe will display the contents of the 3840 x 2400 pixel buffer, not the contents of the 2880 x 1800 screen buffer. That's no longer true: it displays what's on the screen before it gets scaled down. Traditionally, xScope has displayed exactly what's on screen. The good news is that it's hard to tell these pixels have gone missing. Anyone who's worked with Photoshop knows that some pixels are going to get lost in this process. However, when More Space is selected the screen size increased to 1920 x 1200 points it uses a 3840 x 2400 pixel buffer (two pixels for every point.) But the screen buffer only has 2880 x 1800 pixels, so the 3840 x 2400 pixels get scaled down by 66.6% to fit into the pixels available on the screen. With this setting, each pixel in the Loupe is displayed on screen. With the default Display preference in System Preferences (labelled Best) this pixel buffer is 2880 x 1800 which is two pixels for each point on the 1440 x 900 screen.
When xScope works with pixels, it works in the resolution of the display buffer. What You See Isn't Necessarily What You Get Read on to learn how the screen is scaled with different Display settings, how xScope shows the alignment of single pixels, how there are issues with precise mouse movement, and how the tools handle multiple display resolutions. When space permits, pt or px is also displayed.īut under that surface there are a lot of subtle details.
Pixel measurements never show a decimal point.
When points are selected, all measurements are displayed with a decimal point.
0 kommentar(er)
