I don't know what happen with my xcode. Im my controller view only have 3 outlets, but interface builder found 5 outlets. My app always crash in runtime.
Problem caused by previously setted outlet been deleted improperly. You can easily fix this problem by deleting invalid outlet from the storyBoard and also, I can see another issue from your screenshot.You have a breakPoint running on your namePromotionalLabel.Hope this help...
This is what you should do:
Remove all connections from button
Add all connections again, after that your app shouldn't show SIGNAL SIGABRT(which I think it does) anymore
Remove all the outlets from the Outlet section in the above screenshot and then try again to draw and outlet.
if still it cause a problem then create a new swift controller file for that view controller and assign the class to that view controller
I think this is so basic but almost people don't mention this.
The problem is view outlet have to connect to main view too.
Almost cases, it's connected automatically.
Related
I've been developing a macOS app using a storyboard that defines a main window with toolbar and splitview. It's written in Swift 3 -- I have not migrated to Swift 4 yet. The splitview has a pane for graphics and another for a text log; both scroll. I have view controllers for all three; the two subsidiary scenes are tied to the split view with relationships. This worked up until today when I installed Xcode 9 beta 4. (Yes, I have beta 3 in the trash at the moment and can revert)
Upon cleaning the build folder and compiling, I get the error
NSSplitViewController's 'view' outlet should not point to its NSSplitView; use the 'splitView' outlet instead
However, the NSSplitViewController subclass has no outlets defined (its two children arrange to tell it of their existence in their viewDidLoad methods). Moreover, I don't seem to be able to create an outlet between that window and its controller that would have created the error in the first place.
I now also note that the split drawn in the split view controller's scene is horizontal instead of vertical as it had been. I don't see a way to change that. (I can't run the app, so I don't know if it matters. I suspect it does.)
The net result is that I can't see what the error is trying to tell me. The error prevents the application from building and running, whereas with beta 3 it worked. I'm hoping someone can explain what Xcode is telling me and how to fix it.
I did fix this in my own Storyboard. In the outlets window, I saw that the view outlet was indeed assigned to the NSSplitView. I deleted it. It was also assigned to the splitView outlet, so the change did not seem to effect anything.
The warning went away and my project then did build.
I have no idea if this was always that way and compiler update changed or if this was somehow inadvertently set differently in some way. It makes sense in any case, the NSSplitview should be assigned as the splitView outlet, not the view outlet.
I'm trying to create outlets using the Interface Builder, however when drag the UILabel from the IB to my controller's .h file the big lock symbol flashes for a few seconds and it doesn't actually create the bind between the UILabel and the outlet (although the code is generated). I also noticed an empty circle is created by this new definition. When it worked, a filled in circle was created on the side).
I've checked the UILabel and all parent views and have checked that their "Lock" property is set to "Inherit (Nothing)" (and have even set them all to "Nothing").
In the IB the UILabel doesn't show the "x" that appear when a UILabel is locked either.
So I have no idea if I'm missing to unlock something, or what I'm doing wrong to be able to create this outlet.
I don't know if this is relevant, but I'm using a custom view controller, and I'm using this same view controller subclass for 2 different view controllers in the same storyboard. I had no problems creating outlets this way for the first view controller.
Tryed reopening XCode (using 4.4.1) with no luck.
Any help is appreciated!
So are you dragging both UILabels from each View Controller into the same file? I don't think that this is possible, on the second view controller, try to Ctrl drag to the file owner within the IB view, that is, assuming that both views are connected to the same instance.
Also, in your identity tab in storyboard, under Localization Locked, make sure your storyboard locked setting is set to default as mentioned in https://stackoverflow.com/a/11169636/720175
I tried adding a totally new scene and would also get the lock symbol. So it wasn't only the scenes, but the whole storyboard. So a quick search on SO lead me to the answer:
https://stackoverflow.com/a/11169636/720175
I am using a storyboard to connect two different view controllers. When I click on the cell I want it to segue into another view controller (what it usually does). But anytime I link a link a label with an outlet and try to segue, it crashes.
These are some images you may need: http://imgur.com/a/N0lP6.
Thanks in advance.
Click on your terminalsviewcontroller file owner in storyboard and select the connections inspector. Check for a connection called key test that has an exclamation point next to it and delete it.
This page shows how easily I can connect outlets http://developer.apple.com/technologies/tools/whats-new.html in Xcode 4, but I can't get it.
I right click and drag an outlet from the new referencing outlet circle, and into my header where the object is declared, but nothing happens.
Has anyone used this?
Thanks a lot
I had the same problem with the final version of Xcode 4 and solved it by selecting the File's Owner Custom Class before using the drag & drop outlet feature like shown on the screenshot below.
Also, fyi, for outlets the item has to be on a window, not just on the background. It will connect fine, but it will not process the outlet gesture. ort11
https://discussions.apple.com/thread/3054574?start=0&tstart=0
this worked for me
In my case I was dragging the outlet from "Outlets/delegate", but it must come from "Referencing outlets".
I'm working on my first iPhone app and have been able to get most things done. There's one problem that I've run into a few times and I want to understand the issue better.
In XCode, if I go File->New File->UIViewController subclass and make sure that both UITableViewController subclass and With XIB for user interface are checked, then it creates a MyViewController.h, MyViewController.m, and MyViewController.xib.
When I look at this xib in Interface Builder, you can see that the File Owner has an Outlet called view that is already connected to the UITableView. No problem. This all makes sense and is great.
My issue comes when I've changed the type of my class (or done something else) and some how the "view" Outlet goes away. I get an error saying "view not showing up in file owner outlet".
My question is how do I then reconnect the UITableView as the "view" of the ViewController when the Outlet goes away? The only way I've been able to get it to work is to literally start over with a new xib/viewcontroller.
That "view" outlet should be coming from the parent class (in your case UITableViewController).
What do you mean by change type? If you are changing the name of your class, try using Edit > Refactor with the class name selected in Xcode.
In the "Document" window (cmnd + 0) - control + click on file's owner, a weird looking line thing will show up. drag the mouse over to your view and release. a little drop down will come up from which you can set the view to the File's Owner View outlet.
Typically the "view" outlet would be coming from the parent class (UITableViewController). If it's not showing up, then Interface Builder is not connected to your project than this could happen instead.
My problem was due to an edge case as described here: Interface Builder and Xcode integration not working