I struggled with this also, but I’ve found this is solved when you have a non-retina image named image.png and its retina counterpart is named [email protected]. So to fix yours you’ll need to name the first “Default-Portrait-1024~ipad” and the second “Default-Portrait-1024@2x~ipad”. The part preceding the “@2x~ipad” needs to be the same for it to recognize … Read more
If you have an NSImage and want to save it as an image file to the filesystem, you should never use lockFocus! lockFocus creates a new image which is determined for getting shown an the screen and nothing else. Therefore lockFocus uses the properties of the screen: 72 dpi for normal screens and 144 dpi … Read more
NSStatusBar icons (i.e. Menu bar icons) are different from regular app icons. I have not been able to find an NSStatusBar official icon guideline, but I have to believe that the Toolbar Icon guideline for buttons is pretty close. It suggests: Create icons that measure no more than 19×19 pixels. Make the outline sharp and … Read more
No. You need to use the and operator and write that as two queries. You can, however, do this in SCSS, which will compile to CSS, but it will combine them by unfolding them and using the and operator. This is a common problem, and once I first wrote LESS or SCSS, I didn’t ever … Read more
Just in case someone else comes here wanting to know how it can be done programmatically, heres how you do it: Interface Builder Make a height constraint in IB to the desired view and set the constant to 1. Then you will need to CTRL+Drag from the constraint into your custom view or ViewController. Whenever … Read more
Use [UIScreen mainScreen].scale; this will give you the exact scale as per device. In Swift 3 UIScreen.main.scale Cheers.
The new default is Default-568h@2x.png. (note hyphen) There is no other corresponding change. If you need a different image for the new iPhone 5 screen then you have to create it as a separate name. There is no 1x/2x/new phone auto switching behavior.
It would be nice, but this is impossible to do like this. LESS compiles your media queries to actual media queries, so at compile time there is no indication of which media query will be relevant to the browser. After compile time you just have CSS not less so you can’t have variables anymore. You … Read more
According to everything that I’ve read recently, browsers seem to be moving towards the resolution media query expression. This is instead of device-pixel-ratio that is being used in the currently accepted answer. The reason why device-pixel-ratio should only be used as a fallback is because it is not a standard media query. According to w3.org: … Read more