How to setup screen size in Xcode for MacOS application? Do I need to do it programmatically?
I didn't find any settings in Interface Builder related to it or manuals.
Thanks!
I am trying to inject my code for overlayicons in finder in all the three views,
but not able to do it for mac os 10.9 and above, kindly help me in this
for 10.8 and below versions i am able to do.
Maybe try the new Finder Sync? https://developer.apple.com/library/ios/documentation/General/Conceptual/ExtensibilityPG/Finder.html
I have created .icns using .iconset for my Mac app,containing all sizes of icon recommended by apple. But still I cannot see my app icon when I install and launch my app on Mac osX 10.5
Following Apple's current guidelines and using their latest toolset will give you icons that only work in newer versions of OS X. To get a set of icons that includes larger (#2x retina) resolutions and 10.5 compatible image formats, you need to use Uli Kusterer's oldiconutil.
Also, please see this related question--sometimes icon file sizes can be too large for 10.5, and require extra image compression.
How can you simulate a retina display (HiDPI mode) in Mac OS X 10.8 Mountain Lion on a non-retina display?
Search for, download, and install Apple's free Additional Tools for Xcode 8 (for previous Xcode releases search for Graphics Tools for Xcode according to your version).
Note: free Apple Developer account required.
Launch Quartz Debug application.
Go to menu: Window ---> UI Resolution.
Check Enable HiDPI display modes.
Quit Quartz Debug.
Open System Preferences.
Select Displays icon.
If using multiple display, select the configuration window on the display you wish to simulate HiDPI mode on.
Under Resolution:, select Scaled radio button.
Find a desired resolution postfixed with (HiDPI) and select it.
Your display is now running in HiDPI mode, simulating a retina display.
Source: High Resolution Guidelines for OS X
I found the following instructions. It seems to work, and it is much easier than the Quartz Debug approach.
"Enable HiDPI mode in Mountain Lion w/o Quartz Debug"
https://gist.github.com/3191869
In brief, run the following commands, log out, log on, and the HiDPI resolutions are available in the display preferences:
sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool YES
sudo defaults delete /Library/Preferences/com.apple.windowserver DisplayResolutionDisabled
(In my case the first command was enough; the second command just prints an error message.)
Edit: (5/31/2016)
For users trying to do this on El Capitan, please read the FAQ on SwitchRes's website. Also, if something's still not working after you did all the steps in the FAQ, consider uninstalling and reinstalling SwitchResX. That solved the issue I was having on one of my laptops.
Original:
After reading through several forums, websites, blogs.
I am here to present a solution for users with 15" MacBook Pro with Retina display connected to a Thunderbolt Display.
First of all,
Terminal command of modifying plist
Quartz Debug
Holding option and select "Scaled" in System Preferences
ResolutionTab (Mac App Store)
These methods DO NOT work for MBPr with Thunderbolt Display, for whatever reasons.
You will not see the HiDPI options to be selected.
The only tool I found that actually gives us the options is SwitchResX.
However another problem exists here.
Most users with this setup, I believe, are trying to use 1280x720 HiDPI because it's half the native resolution of the TBD.
According SwitchResX's FAQ, in some cases it is not possible to set to this resolution because of a bug within OS X itself.
Here's a screenshot for your reference:
After contacting the developer, he presented a workaround - adding one more pixel - which worked for me.
Install SwitchResX and open it from System Preferences.
Go to Thunderbolt Display tab, and add a Custom Resolutions with Scaled Resolution at 2562 x 1440
Here's a screenshot
Save using command + s. (or simply close the window and use the prompt up)
Restart the laptop.
Go to SwitchResX and select the new custom resolution in the Current Resolution tab. (Sometimes it doesn't show up right away, play around with it and it should.)
Here you go.
I hope this answer gets to users with this setup because it is really frustrating to use 16:10 resolution on a 16:9 display.
For those unable to enable HIDPI on rMBP or new MBA, I experienced the same on my rMBP 15" with Air Display. I solved the problem by installing SwitchResX. With the boolean setting enabled as shown in the referenced gist, the HIDPI setting shows up.
Dragging seems a little laggy in Air Display, but otherwise works great.
Try this
sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool YES
[from here]
If your monitor supports it, it may also be worth setting the DisplayPort version to 1.1 instead of 1.2.
I have a late 2010 Mac Air with a Samsung S27D850 display and had all sorts of intermittent resolution switching issues until I made that change.
As for me its pretty good app that give you opportunity for changing resolution any that you want.
SwitchResX for Mac and MacBook.
This app resolved all my problems with resolution.
Perhaps I'm going crazy here, but I have a desktop mac application which, in one of its windows, has an NSImageView placed in a specific spot (using Interface Builder).
When I run the app on a Mac Mini it appears in the right spot. But when I run it on a Macbook Pro the image view is offset quite noticeably.
I've tried on both Lion and Snow Leopard on two different macbook pros and two different mac minis. The OS version doesn't seem to be a factor. It seems the only difference is that one machine is a laptop and the other is a desktop, but I have no idea why this would affect the positioning of elements.
Is there any reason an app's UI elements would not appear in the right spot when running on a laptop vs desktop?
Or perhaps there's another reason this is happening?
If your display is smaller on the Mac Mini and the window is larger than the display then it could be automatically resized. If that is the case then you should look at the view's autoresize mask to make sure they are correct.