macOS Interface Builder Identity Inspector problem

[pgeppl]

hi
i use Interface Builder 3.2.1 and when i select a ViewController in my .xib file i cannot see the Class Methods and Class Properties tabs on the Inspector Tab ((
i remember that in a previous version this was visible but i cannot find the correct setting to enable this again
can someone help me out???

thanks
pgeppl

 

[szymczyk]

When you say Class Methods and Class Properties, do you mean Actions and Outlets? If so, the outlets and actions got moved to the Library window in Interface Builder 3.2. Click the Classes tab in the Library window to examine, add, and remove outlets and actions.

 

[pgeppl]

hi
and thanks, thats that thing i was looking for!
but i think this is now more complicated than before

can i add here some outlets? because when i change something an save and create code this changes are not written to my code.

pgeppl

 

[Guiyon]

Not in the new version of IB. Apple changed things around so that, ideally, all code changes go through XCode (ie: adding/removing outlets and actions) and IB is used solely for UI changes. IB will pick up any new additions to your header files but things don't work the other way around anymore.

 

[petron]

As Guiyon says they changed it lately.

You simply go to the .h file add the IBAction and/or IBOutlet.
Save the .h file
And now you can use them in the IB for connections and bindings.

Another thing has changed in the IB 3.2 is that...
If you modify your UI in the IB, add a button or a text field. Build and you will not see the changes. Earlier version 3.1 the user has been asked if he wanted to save the IB files before building but not now.
You have to save it by your own initiative before start building, if of course you want to have the changes in the build.

GL

/petron

 

[Guiyon]

Earlier version 3.1 the user has been asked if he wanted to save the IB files before building but not now.
You have to save it by your own initiative before start building, if of course you want to have the changes in the build.

A bit off topic but I actually prefer this method quite a bit because before the "Do you want to save?" would be triggered by ANY unsaved file in the system. It was extremely annoying having XCode ask me if I wanted to save the documents opened in TextMate prior to building the XCode project even through there were no files in common...