I am following a simple swift tutorial that shows how to add a navigation controller to a viewcontroller in storyboards in xcode. This is done using Editor > Embed in > Navigation Controller
The problem is, once the navigation controller is embedded, it cannot be removed. The 'unembed' option is always greyed out. Removing the controller view from the storyboard results in an error. Even if the arrow indicating the first view is pointing to a simple empty view in exactly the same way as when you're starting a new project.
I would expect that there is still some code from the Navigation Controller lingering around somewhere, but how to pinpoint it?
I follow this step.
1) select navigation controller and delete connection.
2) make root view to your view controller
No...there is no source code, don't worry.
If your changes are hot then just Control-Z if not select navigation controller and press delete button.
"unembed" function is for unembedding the "stack" in stackView and not for "navigation controller" nor "tab bar controller"
Related
I am very new to xcode, got stuck in finding the editor to modify the code when created multiple view controllers. Whenever I click on any of the view controllers, I only see same editor contents and cant move to the others for coding.
I searched the web and stackoverflow but could not find a clear guideline on how to manage the editors for multiple view contollers. I have attached a snapshot.
You don’t “find” code. You create it.
When you drag a view controller into the storyboard, it has the default class of UIViewController. It is up to you to make a new code file where you subclass UIViewController, and then to go back to your storyboard and change the view controller to that subclass in the Identity inspector.
I'm following along with the Stanford CS193P Swift/Xcode course using C# with Xamarin.iOS in Visual Studio.
It's gone mostly okay despite some differences, but I am seeing weird behavior when creating segues in the designer that I can't resolve. It is hard to put into words, but basically I control-drag from a button to a view controller, select 'Show Detail' and it creates the Segue - I can see the 'S' in the circle on the Segue line. When I select the Segue, to give it an identifier, the Segue dropdown in the 'Widget' tab of the properties cycles through a few values and the ends up half height with no selected value, and the circled 'S' changes to a 'P' for popover.
A gif better demonstrates this:
Edit:
Steps to reproduce
Create a new Visual C# > iOS > Universal > Single View App project
Delete the default View Controller
Drag a Split View Controller out and delete the default View Controllers
Drag two View Controllers out and create master/detail relationships
Add a button to the master
Ctrl-Drag from the button to the detail and select 'Show Detail'
Select the newly created Segue
Fixed in Cycle9 which at the time of writing is in Alpha (per bugzilla.xamarin.com/show_bug.cgi?id=44401)
first i use the PAGGING library
https://github.com/uacaps/PageMenu
i found that it's the problem , when i connect any button to show another controller it it navigate me to that controller but the navigation not shown , for example back button
i try many solutions and non of them work for example i try to make the menu manual but the back button show but not work
i create button and connect to this action
self.navigationController?.popViewControllerAnimated(true)
didn't work
You need to have a pushViewController first. Ensure that you are displaying your viewcontrollers through push.
self.navigationController?.pushViewControllerAnimated(true)
You do not need to code anything to display the previous controller when you have push.
I have a storyboard project in Xcode. I have added an additional ViewController and dropped in a button, text box, etc. I can get from the initial to the secondary View Controller, but I cannot seem to be able to connect the button to the code. I've tried adding additional classes with XIBs and even from a blank adding in the XIBs. How do I connect the code I have written for a button to do work on the second View Controller?
If you have the button created on the storyboard. You have to make an
-(IBAction)clickButton...
in the .h and .m code files. You can easily connect the code to the button by dragging the line from the dot (in front of the code name) to the button.
If you have created the Button fully in code. You have to specify which code to be executed on click.
[self.buttonName addTarget:self action:#selector(clickButton:) forControlEvents:UIControlEventTouchUpInside];
Here's the answer. You add new files to your project, and just for giggles, we'll call them NewViewController of the UIViewController class. Then, highlight the second view controller in the storyboard, choose identity inspector, and under Custom Class (at the top) you change the class to the name of the recently added NewViewController class. Now, all your code will connect to objects and so on. Thanks again for the help all and now I can rest in peace lol.
Using XCode 4.1 I've come across a crash whenever I try to use a CollectionView.
These are the steps I'm doing:
From a new project, edit the MainMenu.nib file.
Add an NSCollectionView to the window, which also adds a Collection View
Item, and a new View In the new View
Add a control like an NSTextField
Select the control, and switch the inspector to the binding pane.
Attempt to bind something to the Collection View Item.
Once the Collection View Item is selected in the dropdown menu, an
"Internal Error" dialog appears. Attempting to continue from this dialog makes the
binding pane disappear until you restart XCode
Does this happen for anyone else or is it just something I'm coming across?
Is there a way to work around it to allow me to bind to the Collection View Item (I want ultimately to bind to the representedObject value) either in XCode or in code.
I attempted to create a custom NSCollectionViewItem subclass that uses a separate nib file and set that as the itemPrototype of the NSCollectionView but things went very wrong then.
I found that splitting the collection view item view into its own XIB and then rewiring the connections so that the collection view item prototype loads the new XIB will allow for you to create the bindings in interface builder without it crashing. I followed these steps...
Delete the collection view item view from the default xib.
Create a new view and XIB inheriting from NSCollectionViewItem.
Create your collection view item in the new view.
Bind the fields to the files owner of the new view.
Back in the collection view xib, update the properties of collection view item to load the bin name of the new xib.
I'm not sure that it's quicker than doing it programmatically, but it does allow you to manage the bindings without writing code. I've got a few apps working this way now.
I've found a temporary work around:
Select the "Collection View Item" and under the "Attributes Inspector" → "View Controller" settings, set "Nib Name" to "MainMenu".
Once you've done this, it won't crash, and you can set the bindings. Be sure to clear the "Nib Name" setting when building your app.
Yup, I can confirm this bug too, even on Interface Builder 3.
The only workaround is to do the binding programmatically:
[textField bind:#"value" toObject:collectionViewItem withKeyPath:#"representedObject.foo" options:nil];