![]() ![]() In the console you’ll see anything you’ve logged as your app runs. The variables view shows the state of all the variables in scope when your app stops on a breakpoint. Show the debug area – which contains the variables view and console – with ⇧⌘Y. Show/Hide Debug Area: ⇧⌘Y ( Shift + Command + Y) If a clean fails to solve your problem, you might need to show the debug area…Ħ. Clean the project ( ⇧⌘K) and run it again, and maybe – just maybe – your code is actually right. This one is useful when you’re pretty sure the code you wrote is correct, but when you run it, something is broken. open the file in the Assistant Editor (the second pane in the split-pane) by pressing ⌥⏎ ( Option + Enter).open the file in the Standard Editor (the single-file view) by pressing ⏎ ( Enter).To open a file quickly, press ⇧⌘O, then type the filename. ![]() I also like to use it when writing unit tests so I can see both the class and its tests at the same time.Ĥ. The Assistant Editor shows two files at once, and it’s useful especially when connecting Storyboard views to code. Show Assistant Editor: ⌥⌘⏎ ( Option + Command + Enter) It’s what I use most of the time when I’m writing code.ģ. The Standard Editor is the view where you have just one file open, and you can show it with ⌘⏎. Show Standard Editor: ⌘⏎ ( Command + Enter) I do this at least a hundred times a day. Write some code, then build and run your app in the simulator or on device with ⌘R. And, perhaps most importantly, how to get auto-complete to help you out. So you just need to know the relevant keyboard shortcuts in Xcode – the ones that are different from every other editor you’ve used. (Yep, just like in all the other editors out there, these work in Xcode, too.) ![]() If you’re a developer and use keyboard shortcuts in your editor, you probably already know a bunch of Xcode keyboard shortcuts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |