I've heard that the Xcode has an option to change the code and attach it directly to the existing build (run in the simulator for example).
It would be great if you have to move through many screens in the iOS application to get to the same location as before (menu1 -> menu2 -> menu3 -> content)
Could you please give me some info - what is the name of that process?
How can I do it?
How does it really work? - Let's say I've two UIViewControllers - one is with the table (let's call it MenuVC) - list of objects and once the cell was selected the second UIV.C. (let's call it DetailVC) is displayed showing details of that object. Will I've to go back to the MenuVC, do some magic tricks with Xcode and display the DetailVC again by pressing the cell? Or will the DetailVC be changed by itself but remembering the properties I've passed using MenuVC?
That feature was called "fix and continue", but it fell into disrepair and was removed from Xcode 4.
Related
First of all, I would like you to know that the class IS set to the correct file in each ViewController - I know that because it did work before, but then I got a "crash" in Xcode that blinked quickly without me being able to read it before it went off again.
MY PROBLEM IS:
I have a lot of ViewControllers in my Xcode, everything was working fine, I was making some more features to the ViewControllers.
Then I got the "crash" as mentioned above, and it would not show any of the files/classes related to their ViewController in assistant editor.
Assistant editor just said: No Assistant Results. Then I read that I could just show the files inside my XCode project and delete project.xcworkplace and xcuserdata. And I thought it worked at first, but it did not work on every viewcontroller unfortunately - only on some of them.
Now, I still have plenty of ViewControllers left to edit that aren't working, and I would hate if I had to recreate every single one.
Does anyone have a better solution to this? I really hope you do :-)
Make sure you set Automatic not Manual.
There was some related answer but I can't find it. Anyhow: what I do to fix it is to uncheck the Target Membership in the File Inspector for the XIB and then turn it on again. That fixes the issue (in most cases) for me.
Also try restarting/clearing the different caches of XCode.
I was similarly not able to view code/classes relating to the View Controller. In my particular case, it appears i might have caused the issue- I turned OFF Indexing because Xcode was running terribly slow and around that time I started getting the issue and the message “No assistant results”.
To resolve this in my case, I turned indexing back ON and set the Assistant editor to “Automatic”.
To turn Indexing On or Off, open up the Terminal using either of the below commands-
Turn Indexing OFF:
defaults write com.apple.dt.XCode IDEIndexDisable 1
Turn Indexing ON :
defaults write com.apple.dt.XCode IDEIndexDisable 0
From accepted answer regarding Indexing: Stopping xcode from indexing
xcode 9.0
Open project.
Click on "Show the assistant editor".(top right side middle button - circle shape)
Code was show after do second step.
I cloned a project and found that I have the same problem. But all I did to fix it was to just sign the app at Signing and Capabilities and the option for the right View Controller pops up in the top bar of the Assisntant in my View
I am currently watching the video tutorials series by TheNewBoston concerning iPhone development. Unfortunately, he uses Xcode 3 in his tuts so when showing the viewers what exactly should be done to complete certain steps, it is quite difficult to follow along. Here's what I've found that isn't parallel, some of which I am figuring out as I go along, but some is still ambiguous and would be great to be clarified on the site:
Resources is supposed to be the same as 4's 'Supporting Files' folder, however doesn't contain the ViewController files I'm looking for that he demonstrates on. (How do I get to the View display?)
There's no 'tools' top menu bar option
Under this I should be able to find the option item 'Library' which contains 'Attributes' (Where are all of these components located?) - (Actually as I'm going along I'm finding some of these, but for the sake of the site's Q&A style I'll pose the question regardless.)
"Build and Run" button on home toolbar is the same as the "Run" button in 4?
I clicked the Run button and it built, but I have a big white box rectangle after I was told to put the "Bacon" label on the View Controller (which I ended up finding) - what's up with that?
When trying to add an icon to the plist file, the option to do so on the chart is not featured - where is it?
Bucky chooses a View Based Application setting when creating a new project. This is not an option in Xcode 4. What is its closest relative?
What Bucky shows is actually not under the Supporting Files folder, just under the project folder. It will not have the ".xib" ending, but rather a ".storyboard" ending.
True. Sorry.
The Library you are looking for is in the bottom right hand corner of the window. It is one of the tabs that is currently displaying the "File Template Library". Two tabs down is the object library you're looking for.
Yes.
Likely, you were creating display components under the iPhone storyboard, and the option bar just a couple buttons right of the Run button will give you the option to display the iPhone simulator. It is possibly set to the iPad display at the moment.
You must create the property. Click on one of the properties and a (+) sign will display when the item is highlighted. Click it and a new property value will come up to be defined and type in "Icon File." Ergo, you are ready to follow further into the video tut.
Although I am not certain I believe it is known as the "Single View Application" option. It seems to me that they have the same properties.
I have my MainMenu.xib with the Main Menu in it. I also have several NSObject subclasses as Menu Controllers, which are all represented in IB as objects, so that each Menu Item in the Main Menu corresponds to a dedicated Menu Controller
Whenever I try to drag'n'drop some menu item to its Menu Controller header and create an IBAction , Xcode does not give me that option. I suppose it's an Xcode bug, but I'm still confused...
When I created my first Menu Controller everything worked fine. However, now that I've added all Menu Controllers (the very same way as before), only the first one can be "linked" via IB.
What am I doing wrong? Any ideas on how to fix that?
Strange, Make sure the following
you have used the word "IBOutlet" for each to be linkable
clean the code
restart xcode
And just to make it clear,if you think its a bug in your XCode copy, try creating a sample project and see if it also do the strange behavior
on XCode 4.2 when a breakpoint is active while debugging, if I put my mouse pointer over a variable name (into the source code) and a yellow tooltip appears and let me able to view the variabile value (for base type like int, float, and other).
Yesterday I update XCode to 4.4 (for testing my apps on iOS 5.1.1) but when the game stops into a breakpoint, and I move my mouse pointer over a variable, no yellow tooltip was showed.
I think this "fast debugging" is too important, because a programmer, else, for view class fields, need to:
1. Selecting "Local" instead "Auto"
2. Open 'self' object
3. Searching the variabile to view value
this is very slow ...
Anyone know how to solve this issue?
thank you
You may simply need to clean your build folder and have Xcode re-index the project. Hold down Option while selecting the Clean option from the menu, it'll change into Clean Build Folder.
In Xcode 4 (4.2), is there a way to keep the Project Navigator view open and Debug Navigator view open as well. Must a user have one or the other, but not both? And the other navigators?
Apple seems to have decided that if you want to see the debug view, you don't want to see the files in your project. WTH? Am I getting this wrong? Did Apple Xcode UI guys even talk to developers before designing the UI for Xcode 4?
Sigh...
You can indeed have more navigators open at once, if you are prepared to have multiple windows open. I know it's not exactly what you're asking for, but for multiple display setups it's very handy. Xcode provides "behaviors" to help automate this process if you only want certain things showing at certain times.
For example, a common pattern that developers follow is to setup a behavior for "Run starts" that opens up a new window setup for debugging. Start by creating a new tab in your main Xcode window by pressing command-T, and double-click on the tab's title to rename is "Debug", or whatever you like. Then drag that window out (or leave it as a tab if you like), and customise the view as required - for example, for a deb window you might have the Debug area showing at the bottom (or even covering the whole editor view), and remove the toolbar at the top by right clicking and selecting "Hide Toolbar".
Next, go to "Xcode > Behaviors > Edit Behaviors..." and choose "Run starts" in the left panel. Check the box for "Show tab" and enter the name of your newly created tab. You can also ask that tab to automatically show the Debug Navigator, and show the debugger with variables and/or console view. If you like, you can then choose "Run completes" and show the original "tab" (window), which I've setup to be called "Coding", and show the required navigator (in my case, Project Navigator).
On successfully running, Xcode will now open up your new window (or bring it to the front if it's already open) with all the settings you left it with. On stopping, your main editor will be brought back to the front.
There are loads of useful behaviors, so I would really recommend looking through them and taking the time to setup Xcode to suit your style as best as possible. All software dictates to the user how to go about doing things, and the developers can never please everybody when they decide to change the UI. The best anybody can hope to achieve is to customise the interface as best as they can to fit their style of working. If it's still an issue for you, you can either adapt to it, or, if possible, move to something else.
I'm not a fan of every new interface feature in Xcode, but I've "made it mine" with some customisations and I can still be very productive. That being said there are a lot of things that I do really like about it, and for that I can forgive it for some of the less friendly features - after all, you can't please every user.