Every time I nav back to the file tree browser in Xcode 4, whether from debugging, examining the build log, etc., it closes my main "yellow" folder which contains my project sources. Thus I have to dig through multiple levels of folders to get back to the files I was just editing, e.g. before the build. It also keeps auto-expanding the 'blue' folders which are references to trees that I don't need to browse and would prefer to keep closed.
Apple is ignoring its own UI guidelines which say that STABILITY is the primary feature of a good UI. Xcode 4 is so buggy and the UX is so cumbersome it's nearly a laugh.
How can I get Xcode 4.2.1 on OS X 10.7.3 to keep my open folders open, and closed folders closed, in the file tree browser?!
Related
While I am aware that Hot Restart is in preview, it was for quite a while now and my testing never really worked since the first time I've tried it. I've waited for a few VS studio versions to come up, hoping that my issue will be fixed. Since I've kept an eye on issues and haven't seen something similar, I tend to believe that the issue is locally with my setup.
Here is the situation:
I've enabled Hot Restart in VS and added my account, picked the team (after I was added) and everything went fine without errors. I have a free apple account, but after I was added to a Team I was able to obtain automatic provisioning to work.
I've tried to set the debug build options similar to how the simulator was set
I've disabled device specific build as I saw in the docs that it can create problems.
I've installed iTunes just as specified in the docs and when I connect my device to my Windows 10 PC, I can select it from the list.
So basically it looks like everything is set up. I use for testing an iphone 7 with latest iOS version.
Here is what happens:
I've selected different types of output logs hopeing to catch some error in there that could lead me to find a solution.
when starting to build I can see "Building offline for a local device" and I can see my provisioning file details on "Detected signed identity"
I see no apparent error while it compiles and does its job, no complains about signing
then it gets to the IpaCopyToStagingDirectory and there it starts to copy a bunch of files from bin\Iphone\Debug to Artifacts\app.iOS.dSYM where I get the final error: Could not copy the file bin\iPhone\Debug\\app.iOS.ipa because it was not found
If I go to the bin folder, there are many files, including app.iOS.exe, but indeed there is no ipa file. I also don't know why it has two \ on its path.
Any ideas why is not working?
I have several projects I work on concurrently, and have files open for each one. However, having a separate window open for every project is undesirable (mainly because when I Cmd-Tab/Alt-Tab between windows there are 5 different Atom windows instead of 1 and I have to squint and try to identify which one is the project I want).
I know I can open project folders in a single window, but then the tabs for all open files are all open together, which presents an even bigger problem for finding what I want, especially if each project has 4-5 files open.
Is there a way to
have a single Atom window
display multiple projects
display only the open tabs/files for one project at a time, swapping when I select a different project
I found a package that does essentially this: project-plus.
(Tabbing between projects could be improved, but it solves the pain points I mentioned.)
I'm a newbie using Xcode 4.5.2 on a MacBookPro. I'm working on an app based on AMSerialPort, and wanted to change the app name. In Build Settings>Packaging (project and target) I changed Product Name and in the summary I changed the Bundle Identifier.
On the next run it got the below error. The project builds OK. There were still some references to the old name (project and in finder the version col. showed it.
I read a lot of posts on this error and similar ones and none of the answers worked for me. I've tried pretty much every SDK and architecture, I've deleted the scheme and auto-created a new on, done a clean, closed the project, closed Xcode and restarted re-opened the project and no joy.
Trying to get all the names to match I changed the .xcodeproj name, opened it in XCode by double clicking it and now the Run and Stop button are disabled. Cmd B won't build it. All the files show in the list, and I can edit them.
Is there any hope of untangling my mess, or should I just unzip another copy? Doing that puts me back at changing the name.
I'm trying to build a preference pane as a part of learning OS X development. After downloading Apple's preference pane example code and trying to build the project I get the following error:
clang: error: cannot specify both '-fobjc-arc' and '-fobjc-gc'
Turning off garbage collection in Build Settings allows the project to build properly, but once the preference pane example is installed on the local machine it won't start saying,
"You can’t open PrefsPane preferences because it doesn’t work on an Intel-based Mac."
I've tried every combination of architecture (10.6, 10.7) and Objective-C Automatic Reference Counting (Yes, No) and Objective-C Garbage Collection (Supported (-fobjc-gc), Unsupported, Required (-fobjc-gc only) available. While some combinations do allow the project to build, I can't get the preference pane to load.
What are the proper architecture, ARC, and GC settings necessary to build and deploy a preference pane for OS X 10.7 using Xcode 4.3.2?
PrefsPane built with garbage collection turned off and ARC enabled in build setting works on Mac OS X 10.8.2. "System Preferences.app" just shows a message:
To use this preferences pane, System Preferences must quit and reopen.
It's because System Preferences is started with garbage collection enabled by default and if it tries to open a preferences pane without GC it should be restarted without GC too.
So ARC can be used on 10.8 to develop preferences panes.
I just stumbled upon this myself. So turns out (accoridng to Apple dev docs):
All 64-bit preference panes are expected to use garbage collection. Using garbage collection will, in most cases, simplify your code and reduce the likelihood of memory leaks.
In Snow Leopard, the System Preferences application will run 64-bit preference panes with garbage collection enabled, and 32-bit panes with garbage collection disabled.
For more info go to Updating Preference Panes for Snow Leopard and Beyond.
So you can't use ARC. Only GC.
Problem background:
I have a Qt/QML Symbian application targeting Qt 4.7.4, that requires a QML Camera component. The current state of Camera component has a serious performance bug, where once initialized, in order to overlay the camera view on the screen, it forces the whole application to "raster" graphics system. Even when the camera element is closed and destroyed the application remains in raster graphics system, and the whole app takes a large performance hit, rendering it almost unusable (scrolling lists, navigating through pages... ). The problem is gone only after the application is closed and restarted again, which is not really helpful.
As it appears this will not be resolved any time soon (it is marked as resolved only for some small subset of devices, which I doubt as I have a fairly high-end symbian device that suffers the same bug), I have to look into alternatives and workarounds.
One plausible workaround idea I have is to create a separate application, one whose only job is to capture the required image, process it and then closes. Currently I can do this by externally calling the native device camera application, but this is not a viable production solution. The main application would then start this second external application and wait for the result.
The question: is this possible with Qt creator? Packaging two different applications, and deploying them with a single deployment unit, such that the user does not have a complicated installation procedure?
I would have liked to solve this problem with QtCreator a few months ago but I failed. I managed to package two different applications into a single sis file by studying the pkg file format and creating a pkg file containing both applications.
It is worth examining the pkg files generated by QMake for each application and studying the pkg file format.
It is possible to get QMake to generate the desired pkg file. See the documentation of variable DEPLOYMENT, especially the part where pkg_postrules is discussed.
You can add your signed SIS file to another package with this line in PKG:
#"sub.sis",(0x20000002)