I am noobs at Xcode. I am on my second day of learning.
When I start Xcode, the main window has a button for "Getting Started with Xcode" and a subsequent link for "Xcode workflow tutorial"
Now I would simply like the help to be open at the same time as the IDE so that I can read and code. I clicked on the Xcode icon that opened up the original instance, but that doesn't seem to do anything.
How do I get both things to stay open at the same time?
Follow these steps -
Step 1: On opening X-Code, this window turns up-
Step 2: On clicking Getting started with Xcode , gives -
Step 3: On clicking Start Developing with Xcode gives-
Step 4: On clicking the link - Xcode Workflow tutorial present in Write a Sample Application gives-
Notice that in all the process your Xcode menubar remains unchanged i.e.,
Now, Click on File(or Cmd + Shift + N keyboard shortcut) , and select New Project should pop up the windows as shown in Workflow tutorial. Select the application type, saving should bring you new Xcode project. Arranging the two windows side by side should look some what like this -
Now code while you learn from the Workflow tutorial :)
Hope this is helpful.
You can open the documentation window via Cmd-Option-? and search for Getting Started with Xcode there. The option to open the documentation is also under the Help menu.
I generally open a project first and then open the documentation afterwards, if necessary.
Related
enter image description here
iOS-simulator is not listed all the time. sometime its showing most of the time its not there. not doing any specific changes in my machine. Simply when i restart VS app. its missing.
tried unload & reload the ios project. still the same.
complete reinstall visual studio & xcode from scratch.
tried update xcode.
Nothing helped from above suggestions.
Would be really great help if someone could help me with this issue.
I've encountered the same problem several times and here are some of my suggestions:
Did you try switching to your Android project then switch back to iOS project? This should be the simplest way
In your iOS project options, create a build configuration specifically dedicated to iOS Simulators only. Make sure to set Linker behavior to Don't Link
Quit Xcode and Visual Studio first. Open Finder, press Command + Shift + G, paste the following path: Users/YourUserNameHere/Library/Developer/Devices/ You'll see a bunch of folders with encoded folder names and a file device_set.plist
Next delete all the folders in Devices directory, then open device_set.plist by double clicking it. This should open it in Xcode. You'll see a bunch of key-value pairs under DefaultDevices and DevicePairs, click on the arrow on the left side and delete of the devices listed there by hovering the mouse over a category and click the minus (-) button next to it.
Press Command + Shift + 2 to open Devices & Simulators Window (Alternatively you can choose on menu Window -> Devices and Simulators. Choose Simulators on the left sidebar. Delete all the simulators if there's still any of them showing up. Then create several simulators, ones that you really need for debugging your app. Quit Xcode, reboot the machine, open Visual Studio again.
Sometimes in Xcode 6 Assistant Editor -> Preview stops working.
Showing just "No selection" even if no errors and Storyboard is ok.
Why does this happen?
The reason is "?" (questionmark) in Project's name (maybe there is a bug with other symbols – didn't check it).
You can try to rename Project or just create new one with name without "?" in it.
You must to Kill Xcode from processes for complete and then open it again. You can do it with Activity Monitor o CLI. Voila! - Preview is working again.
Don't just close Xcode keeping the app working. Sometimes also works closing with CMD + Q.
I had similar problem, but fixed it
You must open the xib or storyboard file in both assistant editors. Click the navigation button in the second editor (either the bottom or the right editor, depending on how you stack the assistant editors) and choose Preview to get the preview to appear.
thanks to
http://meandmark.com/blog/2014/09/xcode-6-no-simulate-document-in-interface-builder/comment-page-1/#comment-2883
I have played with Xcode 6 for a while and I encountered similar problems occasionally. I never used special characters in project or class names but the problem sometimes happens.
Now I have to test all ViewControllers at starting point to see if the Assistant Editor work. If not, I will just delete the class file and recreate the same one, it usually fix the problem.
Hope this can be fixed soon.
I'm newbie to ruby and rhomobile.
I'm debuggind succesffuly using the simulator, I can set breakpoints, etc... All works fine except I can't debug inside the framework code.
How can I debug through the framework code in a rhomobile app? How can I configure rho studio so I can debug inside the framework?
I'm a newbie with ruby and eclipse.
More detailed:
My problem happens when I try to debug functions inside the framework. For example: I put a breakpoint in a model.find(:all). The debugger stops here, but when I want to debug then find method it doesn't enters it, it simply executes and continues in the next instruction. In keys terms, I want to make a step into, but it makes a step over. If it helps you, in edit mode, when I press control+left mouse button over a "Rho::RhoController" in a line like this: "class TestController < Rho::RhoController", it doesn't open /rhodes-3.2.1/lib/framework/rho/rhocontroller.rb, where the source code of this class is.
First you need to install rhostudio, once ure done with that. You need to run your application through Rhosimulator which is a really fast simulator than native blackberry, android & ios simulators.
Please follow these steps :
Select Run » Debug Configurations… from top menu
Find ‘Rhodes Application’ section on the left and add new (or modify existing) configuration
On ‘Common setting’ tab select a project by clicking ‘Browse…’ button next to ‘Project name:’
Select ‘Rho simulator’ as the platform
Click ‘Apply’ and then ‘Debug’
Its good that you have already added breakpoints in your .rb files which you can now view in log in Console window.
I need a offline version of http://developer.apple.com/library/ios/navigation/
Does something like this exist? thank you
You've already got an offline version of the Doc, if you have Xcode installed in your system.
In Xcode, goto Help --> Developer Documentation. Shortcut: Option + Command + ?. This will show you the documentation page loaded in Xcode itself. Select the Home button at the top of the toolbar. It will show a drop down list of reference libraries available. Select iOS library from the menu. It will show you the page you want.
In Xcode, Option + Double-Click on a symbol: Opens the doc for the selected symbol in a small window. Clicking on the book-like-button, the second button from the top-right corner of the window opens the reference page of the symbol. That button is enabled only if the documentation available for the symbol.
A more up to date question and answer: XCode Documentation - Offline Reading
The shotcuts Simon describes still work, but the Help menu has changed.
I am attempting to use the 'Fix' command found in the 'Run' menu in Xcode to modify my running code without having to rebuild. I have read apple's documentation on it but following their
'typical fix-and-continue workflow:' (http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/XcodeDebugging/230-Modifying_Running_Code/modifying_running_code.html) doesn't seem to be working for me...
Here is what i am doing (from scratch):
- create view-based project in Xcode
- create click event to trigger a function that just logs some output
- run in simulator with debugger (command-Y)
- click 'pause' in the debugger.
- add another log (or some other simple change) to the function
- save modified code
- select 'Fix' from the 'Run' menu
- click continue and click button
The added log doesn't appear...
Not an answer, per se, but this "Fix and continue" system is disappearing in XCode 4. I wouldn't invest a lot of time in learning to use it, or developing a debugging strategy around it.