An oft reported bug I guess, so you're not alone.
After deleting an outlet, did you try an 'option-clean build folder' to see if that moves thing along? Deleted derived data?
If still no joy, try restarting Xcode.
KMT, thanks for your response. Yes I used the "Clean" function, which I find myself doing to much in Xcode. Yes I've restrted Xcode and even rebooted my laptop. No joy from any of these actions.
I don't understand your comment, "Deleted derived data?". What is it, where is it, and how do I do it?
> Yes I used the "Clean" function
A simple clean is rarely useful and not what we're suggesting.
Instead, hold the option key, then use the Product menu and choose to 'clean build folder'.
>I don't understand your comment
It's manual, now, so don't bother if you don't already understand.
If you delete accidentally, either in IB or in code, and realize rapidly, undo works well to restore everything.
Otherwise, it may be more difficult: if you deleted in the code (or just change the name of outlet) you need to clear the connection in IB and then perform an option clean as KMT advised.
To rename an outlet I usually do:
- delete the connection (right click on object in IB and click on the x in front of outlet name)
- to establish the connection again, it may not work by dragging from the bullet in code to the object in IB; but it (usually) work by ctrl drag from object in IB to the name of the outlet in code.
Hey Claude, What I've found is that no matter what object place on the VC screen, I can't make any corrections to them. I get the message described in my original post. By the way, I tried the 'clean folder' method in addition to the 'clean' option, and none solve the problem. So, once again, I'm forced to rebuild the VC and VC.swift files. This is a real pain in the fanny!
Since I'm forced to recreate the scene with the connection problem, do I need to do the VC AND VC.swift, or can I get away with re-creating the VC only. It appears the problem is in the VC, and not the VC.swift. However, it could be under the covers of the VC.swift, too.
Thanks for your responses, Claude. Probably what I learned most is be EXTREMELY careful when working with connections, because Xcode is broke when it comes to making any changes to them.
The only workaround I can offer others for the situation is to type in your link in your viewController or windowController file:
@IBOutlet weak var taxFormPopUpBtn: NSPopUpButton!
then, in Interface Builder, right-click Placeholder for the File's Owner and you should find the Outlet there. Drag from that outlet to your control/view to make the connection.
I cannot see why Interface Builder stops working the other way round. I've looked at the source code and cannot see any remnants of the old code.