In Xcode 6.1 I'm seeing a "3x" and "All" resolutions available for my Mac OS X target. I wonder if the "3x" option is used for Mac apps? If it does, which configurations that calls for the 3x artworks?
Does the new 5K iMac makes use of those 3x artwork resolutions? Or some Mac pro configurations?
If those 3x artworks are not present, does it render the PDF version instead of upscaling the 2x ones?
The only reason 3x is available is because in the Devices attribute, you've chosen Universal – if you choose Device Specific and check only Mac, you'll see only 1x and 2x.
The 5K iMac just uses 2560x1440 #2x (hence 5120x2800 pixels), not 3x in any case. iPhone 6 Plus is the only device to make use of 3x images, as far as I know.
Answer accurate at time of writing! (17/04/15)
Related
Recently i upgraded to mountain lion.I want to open my old projects in older version of xcode 4.3 and i don't want to use xcode 5 for some reason.
Is there any way to open xcode 4.3 only. I have installation file of xcode 4.3 if its needed to reinstall.
It gives alert "This installation of Xcode 4.3.2 requires Mac OS X 10.7 Lion."
I know how to run my projects in other versions with old simulators... but only need 4.3
Any Suggestions?
Ignore the snarky comments by people like matheszabi; there are good reasons to support the millions of units of older devices. Tip: If you are looking at picking up older devices, you'll want to target iOS 4.2.1 not 4.3, as every device supporting 4.3 can be upgraded to iOS 5. See Highest Version of iOS Supported.
Virtualizer
To answer your question, "Any suggestions?": Use a virtualizer like Parallels, Fusion, or VirtualBox to run Lion, Mountain Lion, or Mavericks in a virtual environment. This arrangement has many advantages, including resisting the pushing and shoving of Apple to constantly upgrade our OS, Xcode, and iOS targets.
Another advantage is a pristine working environment with its own clean Keychain, Desktop, and so forth having only items related to Xcode project(s). All my own personal stuff is kept to the real Mac. I think of the real Mac like I do my home, with personal property, while I think of the virtual Mac as my office space, my cubicle, having only work-related items.
The one thing you'll need is memory (RAM). If you want a 3 or 4 gig virtual Mac, you'll need about that much space unused on your Mac. By unused, I mean the green colored piece of pie in Activity Monitor.
My Experience
For my current project, I run Xcode 4.6.3 targeting iOS 5 & 6 in Parallels 8 (9 is now available) on a Mac mini (Late 2012) with 16 gigs of memory and i7 quad-core with 8 virtual cores driven by Mountain Lion 10.8.5 on the real Mac, while the virtual Mac has 4 gigs of memory and 2 cores. For the most part this works very well. A few bugs, but no show-stoppers.
The only bad bug is that copying text from the real Mac and pasting into the virtual Mac appends an extra mysterious invisible character that wreaks havoc, including preventing compiling of Objective-C code. I routinely do searches for that evil character, and try to make a habit of hitting Backspace after pasting text brought over from the real Mac.
Another bug: Horizontal scrolling by finger-swiping on my Apple Magic Mouse does not work in the virtual environment.
But Parallels 8 + Mountain Lion + Xcode 4.6.3 works well. You can plug in an iOS device for direct debugging via USB cable – Parallels asks whether you want the connected device to be seen by the real Mac or the virtual Mac.
I've also run earlier versions of Xcode 4 on Lion (besides Mountain Lion) in Parallels 8.
With this arrangement, I am free to consider upgrading my real Mac to Mavericks while keeping my Parallels 8 + Mountain Lion + Xcode 4.6.3 work environment intact. Though, I may need to shell out some money to upgrade my Parallels 8 to the new version 9. No such thing as a free lunch! (But this arrangement comes close)
Backups
Tell Time Machine to avoid backing up the 20-50 gig file that is your virtual Mac's hard disk. Instead, do an occasional backup of that large file. More often, make a backup of your import work files and Xcode project, copying off to Dropbox, Google Drive, or external hard drive or SD card. If that file that is your virtual Mac's hard disk ever gets corrupted, you may lose everything. So backup religiously – though I'm sure you do so anyways now. ;-)
Looks like Xcode 4.3 doesn't know about Mountain Lion, the fix would be downloading and installing Xcode 4.6.2 from developer center, which surely supports it.
I'm new to Mac programming and am really getting confused on what is the correct way to capture any webcam.
Learnt:
On Windows - Directshow filters are the only recommended way.
On Mac, there are atleast three frameworks. This is what I've understood by searching through the forums. Please correct me if I am wrong.
QuickTime - 32 bit applications only
QTKit - 64 bit applications only
AV Foundation - OS X 10.7 and above.
(I've gone through some posts which said - when QTKit is used, some webcams were not even recognized. But did't understand what to do)
Requirement: Capture any Webcam (internal or external - any vendor) on Mac OS X 10.7 and above in a 64 bit application, which is built on OS X 10.6 (due to large chunk of frameworks not migrated to Xcode 4 at the current moment code has to be built on Xcode 3.2.5 on OS X 10.6. We are planning to migrate to Xcode 4, but it takes more time and cant fit it in the current release schedule). So, I cant use AV Foundation.
Question: If we use QTKit alone, will the application be able to capture all webcams? Or some webcams with 32 bit drivers or drivers which support only AV Foundation fail? Is the right way to capture on Mac is to implement the capture functionality using all three frameworks?
I've got MacBook Pro 2011, 15" i7 2GHz 8GB Ram 1333 MHz OS X Lion 10.7.2 all updates installed released to this date.
I have done everything what I can to minimize RAM consumpsion and the only problem I've got at this point is when I run Xcode. I had 4gigs of RAM, than bought 8 gigs and always 've got 10-30 MB of free memory after 3-5 minutes of Xcode running and PAGE INS are 300MB - 700MB. I tried to switch to 32-bit running mode but no change. Can anybody help me please?
Yes. One way is to disable indexing, another is to reduce the number of build processes. These are hidden preferences in Xcode 4 which I have detailed here:
Hidden Features of Xcode 4
I've also made a pretty extensive write up for improving and working with Xcode's resource issues:
Why are xcodebuild and Xcode 4.2 so slow?
So after deciding to install Xcode 4 on my '09 mac mini because of how useful its instruments feature is (opengl stuff), it turns out that my mac mini only barely manages to run it.
In other words, it's crippled. I'm still here waiting for my program to run on the iPhone, and it's stuck with some "NSAutoreleaseNoPool" message.
The thing is, normally I would ask on how to fix that message, but currently XCode itself is frozen and not responding to anything.
Will upgrading from this old mac mini (it only has 1GB ram) alleviate this issue? Would the new mac mini with a 4GB ram upgrade suffice? IIRC it's core 2 duo 2.25ghz as opposed to my current 1.83ghz, would that make enough difference?
edit: not to mention, indexing cripples the performance to an extreme level
Especially when dealing with running VMs (i.e. an iPhone/iOS emulator), RAM is usually the choke point in my past experience.
I would think 4 Gigs of RAM should do it just fine. My Mac Book Pro has 4 Gigs of RAM and runs android emulators all the time and I'm still able to multitask.
Go into an Apple store and tell the guy you wanna demo the latest gen Mac Mini running XCode and its emulators and see if the performance if worth the investment. Its all Apple hardware/software so I don't see why they can't help you out.
8GB Ram
Since you can get already even 16GB Ram in Mac Mini (at least the newest), I cannot see why not take it? More here. Related threads mention very painful experiences with 1/2/4Gt particularly with Xcode 4. As far as I see it, 8Gt is becoming really a must-have, particularly when Xcode turns to 5.
Xcode 4 experiences
Minimum spec for Xcode 4?
http://www.cocoabuilder.com/archive/xcode/303406-xcode-4-system-requirement.html
https://apple.stackexchange.com/questions/14923/what-is-the-minimum-hardware-needed-to-run-xcode-4
Similar gettings slow threads
Xcode 4 configure to use less RAM?
Xcode suddenly very slow
I want to Install any smooth working version of XCODE(for Iphone Apps development) on MAC machine having configuration as follows:-
MAC OS Z1-9.2.2,
Built In RAM-128 MB,
MAC OS ROM 9.0.1.
What are the feasibilities with that MAC.
Please help as I am just One day old for MAC.
No, it's not possible. It requires a modern Mac OS X. Xcode4 requires at least Snow Leopoard, and IIRC so does the current Xcode 3.2.x.
Even if it were possible, my Xcode4 right now occupies about 590MB of RAM at the moment of this writing. You wouldn't want to run something like that on a system with just 128MB RAM.