Interface Builder - no Inspector

I have a table view in IB and a data source class in XCode. I have made an object in IB, too and to connect these 2 I need to make this object an instance of the data source class. My problem is that the Inspector won't open no matter what I do, neither via the toolbar nor via the main menu. I'll fill a bug report right after writing this, but if you knew a solution or workaround to this I'd be very thankful.

well, I hate to be asking what may be obvious...
has inspector ever shown up for you? have you tried window menu - bring all to front?
do you ever work on multiple or different sizes of monitors? it could be off the screen somewhere.
I'd try bumping up to the highest res you can and if you still can't find it, you may need to find out where IB stores the window locations so they can be reset.... I don't know that uninstalling and re-installing would have any effect but it may be worth a shot if you find no other fix

Similar Messages

Inspector and Library Window are always on top in Interface Builder

Hi,
Inspector and Library Window are always on top in Interface Builder. I use a small 13" macbook screen most of the time and I don't have a lot of room. Just wondering if I can disable this so I can have my work area hover over the library and inspector when I'm not using them.
Thanks

I still have not been able to figure this out. The best I could do is resize each of these windows to really small and maximize them when using them. But they're still always on top and this is really annoying.

Load Class in Interface Builder 3

Hello,
i am trying to get started with Cocoa after having worked a while with Xcode & smaller AppleScript based projects.
As my idea was to create a menubar-based (NSStatusItem) service app for myself i started with this tutorial:
http://files.semaja2.net/NSStatusItem%20-%20ObjC.html
Unfortunaly it seems like there was a change in Interface Builder regarding loading Classes from Version 2 to IB version 3
The tutorial tells me to (about the middle of the tutorial):
Rename the “NSMenu1” to “StatusItem”, following this in “Interface Builder” >>choose from the menu “Classes > Read Files..” now select the AppController.h >>file, Once the file has been read it should change out project view to “Classes” >>from here find the AppController item and right click on it and select >>“Instantiate AppController”:
I was able to follow the tutorial until there without problems but it looks like the Classes-Tab is gone in IB 3.x.
So i feel somehow unable to finish this small tutorial.
how would i do this step in Interface Builder 3.x ?
Any help is heavily appreciated.
Best regards
fidel

fidel-castro wrote:
I was able to follow the tutorial until there without problems but it looks like the Classes-Tab is gone in IB 3.x.
So i feel somehow unable to finish this small tutorial.
how would i do this step in Interface Builder 3.x ?
You're right, this has changed. I'm currently using IB 3.1.1 but I believe the changes appeared in IB 3.
Once you've done the "Read class files" and selected your AppController.h file IB should know about your class.
In order to instantiate your AppController in IB first go to the Library window and find the "NSObject" (it will appear as a blue cube). Drag one of these NSObject's from the Library window and drop it into your MainMenu.xib window along with the other icons that appear there (File's Owner, First Responder, Application... etc).
Now you will have created an instance of an NSObject in your MainMenu.xib file. And, since your AppController class is a subclass of NSObject (and IB knows this since you've had it read in your AppController.h file) you can now change this NSObject instance into an instance of your AppController.
Select the NSObject icon in the MainMenu.xib window then go to IB's Inspector window and click on the next to last icon in the top tool bar. This should change the Inspector window's title bar to say "Object Identity" and the Class Identity in the first text field should be set to NSObject. You should be able to type "AppController" into this field (or click the popup and it should show up in the popup list. Once you've done this it will transform the NSObject instance into an AppController instance.
You'll see another slight difference between IB 3.x and the tutorial when you do the <Control>-Drag between items to connect up the outlets and actions. Instead of finalizing the connections in the Inspector window like the tutorial says you'll get a small popup window right next to the item you're connecting to that will list the available outlets/actions you can connect to. Simply click the one you want. You can still double-check your connections in the inspector window though.
Steve

Creating an attribute editor like panel from Interface Builder

The Attributes Inspector from Interface Builder presents the user with a great set of options that are neatly organized in folding panels. I really want to do something like this for a project I'm working on to help organize a large set of options that I plan on presenting to the end user.
Only problem is I have no idea what this widget is called or even if its available from Cocoa. I thought it was a NSRuleEditor but I've seen no examples so I'm not sure. So if someone could help point me in the right direction that would be awesome. If you know of an example project in the Examples folder that would be even better. Thanks a lot.

The IB toolpanel is just built out of stock IB parts but there are quite a few of them. As far as I can tell it's just an NSPanel with a toolbar at the top and then at least one NSSplitView with an NSScrollView inserted into it.
To add something like this to your project - although I would recommend starting simpler for learning - simply drag an NSPanel into your IB window and then drag an NSScrollView on top of it and it will fill the NSPanel and you can modify it from there. You can also drag an NSScrollView directly into your nib and work on it and then drop it on the NSPanel if you want. This might make the process easier/more clear for you. If you put an NSTextView into the window it will automatically show and hide scrollbars depending on content unless you tell it otherwise.
Custom views can be confusing but since NSPanels can be made to show themselves as soon as a program launches (I think this is their default state) your content should show up automatically which makes it easier than creating regular windows and then worrying about showing their contents.
Do this help?
=Tod

Using Interface Builder to Inspect a New Object?

I am having a major frustration following a Stanford demo on using Interface Builder. The demo shows how to create a simple slider object with a value. But when the demo pulls up the Inspector Window to examine the new Object, in the Stanford demo the inspector window has panes for CLASS ACTIONS and CLASS OUTLETS, whereas my inspector window, identical in every other respect to the demo window, doesn't have these two panes. Help!!!!!!!!!

The first lecture gives information about joining the developer program and there are forums similar to this at their website. You can also find forums on private sites on the web that are following the courses and have their own forums for asking questions like this.
Try one of those paths and you should find more help than on here. This is just end users helping end users not delopers.
Jason

Can I no longer browse classes in interface builder?

in tiger, I used to be able to browse classes in interface builder, and from their I could create subclasses, and create actions and outlets. then I could create files for the classes from the classes menu. then when I went back to xcode I would have empty class file templates that I could then write the methods for.
also, I could easily instantiate my class via the classes menu.
alas, now I cannot find these features. have they dissappeared entirely? is there an equivilant way to do this?

I found that disturbing too...
However the system changed completely. You can no longer define the super-class directly in Interface Build, however you can still define classes there with IBOutlets and IBActions.
First, to instantiate a blue cube as a custom object, simply drag a blue cube from the Library windows inside : Library --> Cocoa --> Objects & Controllers --> Controllers.
To set the class, go in Identity inspector (CMD + 6) here you'll be able to define the class name, its outlets and its actions, you can even define the action argument type (sender) here, however, weirdly, they took the ability to add the colon directly at the of the method name, so you'll have to add it yourself.
However, Apple documentation advise you to add methods and outlets directly in Xcode and not in IB, "Whenever you want to create a new controller class, or add an outlet or action to an existing class, do it in Xcode."
Indeed, if IB is opened at the same time, it will update the class's outlets and actions directly, Xcode and IB are more binded together than before.
Message was edited by: PsychoH13

Interface Builder SubClassing

I recently installed 10.5 and Xcode 3.0. When I went to start my first Cocca app I discovered that when I opened the main menu nib with IB the panel that displays instances and classes etc. did not have a bar for selecting:
instances classes images sounds nib.
Is this a new way of doing things or is there something I needed to install or set?
How do I subclass, and create object files?

No, you don't need to install something else. Interface Builder 3 is just made like that.
You can no more subclass a class directly in IB, however you can still build the basis of your class.
You have to go in the Identity Inspector (cmd + alt + 6) of your object, you can set the object's class name, you can also set its actions (with the type of the argument) and set its outlet.
The you generate class files using File --> Write Class Files…
Now, IB is completely bound to Xcode, when you use IB, you usually have Xcode opened next to it. If you add an outlet or an action directly in a class that IB knows it will update its data in IB on the fly, so it's better from then on to use Xcode to modify class for which the class files are already created.
NB : you need to set the superclass in Xcode, you can't do it in IB.

Interface Builder Library?

Is there a library of additional items which can be imported into Interface Builder, either from Apple, third-party, or open-source projects?
Apple provides all the basic elements, but either I haven't learned how to take full advantage of advanced use of the existing items, or some other common items are missing. I would think with the insurgence of new developers and platforms, specifically the iPhone and Cocoa Touch, there might be additional packages or libraries available.
For instance, I like the revolving picker, but for something a little less flashy, a simple pop-up list similar to a web-based select, would be a great little item, allowing for single or multi-item selections.
I'm sure I'm not the first or only developer interested in being to re-use well crafted elements.
Another example is the info light or info dark UIButton. Since I didn't feel comfortable crafting my own programmatically, I put an info light button in my xib file, and programmatically put an opaque circular graphic right over the info graphic, userInteractionEnabled=NO, and voila, functionally the same, but the screen presence is different.
Having a larger library seems like just the thing.
Are there any out there?

Have you looked over Adding Custom Objects to the Library in the Interface Builder User Guide? That feature doesn't provide everything you're asking for, but it might come in handy.
It might be good to remember that IB doesn't create objects, and the xib file doesn't include instructions on how to create an object. IB just specifies an object which must already be defined somewhere. So any 3rd party icon library would not only need to have an API for IB, it would also need to include a framework or static library to actually create the new objects represented by the icons.
Another point to remember is that the appearance of an object in IB doesn't determine what an object's class will be at runtime. That's determined by the Class you specify in the Identity Inspector. So if you have a custom class in your own library, you can use that class in IB by dragging an "Object" (cube) icon into a window, then setting that icon's identity to the custom class.
Hope some of the above is useful to you!
\- Ray

Adding navigation items to view controllers in interface builder - pwnd me

I am perplexed by Interface builder. I had SDK version 2.x (can't recall now) and just upgraded to the newest 3.1 and now things do not work the same.
So that I could have a custom navigation item applied to my view controller, I have followed the instructions here:
http://developer.apple.com/iphone/library/documentation/DeveloperTools/Conceptua l/IB_UserGuide/EditingNibFileObjects/EditingNibFileObjects.html
in section entitled "Configuring the Views for Additional Navigation Levels"
When I try to load the nib at runtime I get this error:
[* Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '-[UIViewController _loadViewFromNibNamed:bundle:] loaded the "EventCreate" nib but the view outlet was not set.']
The view is set on the controller; however, I did not do anything to set the file's owner since the before-mentioned doc does not say anything about that. It seems the view must be set on the file's owner to make it work. This is confusing.
I've noticed that the nibs I had set up using the previous release (2.x can't remember now) aren't totally supported in the way I had them set up with navigation items. In IB, I would set the File's Owner to by view controller and then I could drop a navigation item in and connect that right away to the controller, and the controller had a navigation item outlet exposed by default. That doesn't appear to work any more. When I open my older nibs (xib files) the navigation item outlet shows up in the inspector for the controller BUT its greyed out, as if obsolete. There's no navigation item outlet showing in IB anymore, it seems when building new xibs. So, I don't know what to do here.
Can somebody help me?

crouchingchicken wrote:
I would set the File's Owner to by view controller and then I could drop a navigation item in and connect that right away to the controller
Yes, I agree. The nav item used to show up as an outlet of any view controller.
When I try to load the nib at runtime I get this error:
The problem with the doc is this line:
To push a new view controller at runtime, _create a new instance of your custom UIViewController subclass, initialize it with the nib_ file you created for it, and push it on the navigation controller stack.
The underlined portion can lead us to believe we can alloc and initWithNibName:bundle: as we would when File's Owner is a proxy for the controller we create in code. But that won't work in this case, since the controller we want is the one that's created from the view controller object when the nib is loaded. In other words, we don't want to alloc a new controller, we just want to grab the object made from the nib. Here's what to do:
// RootViewController.m
- (IBAction)nextView {
NSLog(@"nextView");
// SecondViewController *viewController = [[SecondViewController alloc]
// initWithNibName:@"SecondViewController" bundle:nil];
NSArray *nib = [[NSBundle mainBundle] loadNibNamed:@"SecondViewController"
owner:self options:nil];
NSLog(@"nib=%@", nib);
SecondViewController *viewController = [nib objectAtIndex:0];
[self.navigationController pushViewController:viewController animated:YES];
// [viewController release];
Be sure not to release the object obtained from the nib, since we didn't alloc it. Top level objects created from a nib are autoreleased. You can put some logging into the second view controller's dealloc to verify it gets dealloced when popped:
// SecondViewController.m
- (void)dealloc {
NSLog(@"dealloc: %@", self);
[super dealloc];
- Ray

Xcode 3/Interface Builder - Adding classes to NIB file doesn't work

I'm attempting to learn Objective-C and Cocoa GUI through Apple's "Currency Convertor" tutorial. I'm currently at the "Add the ConverterController Class to Your Nib File" step, and I add ConverterController.h to the Interface Builder project (both by Read Class Files and dragging) and... nothing happens. The tutorial clearly states that the class should appear as a new icon in the MainMenu.nib window. I've tried researching this problem, and it appears to be quite common, however every fix isn't really a fix at all. They all involve using the Identity Inspector for something, which appears very complicated, and is otherwise uncovered in the tutorial. It occurs to me that anyone knowing enough to be able to use this fix wouldn't be reading this tutorial, thus making such answers moot. Any help anyone could provide on this issue would be appreciated.

The tutorial you linked to should work fine except that they've just got the illustration (Figure 5-3) in the wrong place.
The placement of that illustration implies that you should see the instance of your class in the MainMenu.nib window right after doing step 2 (where you read your class file). But that's not really true. In reality it's step 3 that gets you the blue box in the MainMenu.nib window and steps 4 and 5 that will transform it from an "Object" into a "ConverterController". Steps 3, 4 and 5 are exactly what Thomvis suggested that you do earlier.
Steve

Interface Builder w/ Xcode folder refs

when i set up xcode with folder refs interface builder does not see my images in the dropdown list. i actually have to type out the path and ib will show a broken image. is there anyway to fix this?

Note that *AppleScript Studio* has been deprecated in Snow Leopard - AppleScriptObjC is the new framework. You can still edit Studio projects, but the project templates have been removed and you will need to enable the AppleScript palette - see the release notes.
Assigning a handler (IBaction) to a button (or any object) is pretty easy - create a handler in your script that takes a single parameter and name it with a trailing underscore (the naming conventions are also in the release notes), for example:on doButtonStuff_(sender) it will appear in *Interface Builder* under the *Connections Inspector* for your application delegate - from there you can make a connection from your object to the handler. MacScripter has some tutorials for AppleScriptObjC in Xcode, and I also have a button example project (it's not much of a tutorial, though).

UITableViewCell and the Interface Builder

I'm trying to use the Interface Builder to create a UITableViewCell but am having problems.
I can create the UITableViewClass in my .xib file, connect the reference outlet and reuseIdentifier using the inspector. The problems occurs when I try and render the cell with this method...
- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath
Since the interface builder creates the TableViewCell automatically, I should be able to call...
UITableViewCell *cell = [[[UITableViewCell alloc] initWithFrame:CGRectZero reuseIdentifier:@"priceCell"] autorelease];
..from inside the tableView:cellForRowAtIndexPath method and get that cell instance. But none of changes (Color, accessory view, etc...) I made to the table view come through.
Has anyone got UITableViewCells created in the interface builder to work?

Just an update to inform people of some of my findings.
I had originally, before gkstuart's post, had added a UITableViewCell instance as a child of my view in IB. I then tried to use the cell via an IBOutlet in the UITableView in my view. This is when I was getting a completely blank screen when running my application. I then adopted gkstuart's idea and created a cell factory class, but without thinking, I used the same cell instance on each call to my 'newCell' method. Once I updated the 'newCell' method to load the nib file on each call to 'newCell' everything seems to work fine. As a note, the nib file loaded by 'newCell' is a simple nib file containing only my custom cell definition. It does not contain any views. Gkstuart's method of loading custom cells is unfortunate, because you can't seem to use the reusable cell theory when working with cells defined in IB. This is obviously something that needs work on Apple's side.
As a test, I removed my custom cell definition from my original view nib. I then added a new top level instance of UITableViewCell, by dragging the UITableViewCell item to the window with the File Owner icon. After updating the custom cell definition with the appropriate class and outlets, I tried my original method again. I no longer get a completely blank screen, but it still doesn't work right. I now get a single cell in my table view, which happens to be the last cell in the list. When looking at it with the debugger, dequeueReusableCell never returns my cell instance so I am reusing and returning the same cell for each call to 'cellAtIndexPath'. I tried to manually call the cells 'prepareForReuse' method but this didn't seem to have any affect.
So at this point, I am going to continue with the cell factory methodology until Apple either fixes the current problem or informs people on the proper way to use IB with custom UITableViewCell's.
As a side note, I am going to start blogging about my experiences with the iPhone SDK over at iphonesdktrialsandtribulations.blogger.com.

After upgrading to Mountain Lion, Interface builder starts up with an error every boot.

I've got a late 2008 Macbook Unibody 13", and a few months back I upgraded from Snow Leopard to Mountain Lion. Ever since the upgrade, at every boot up Interface Builder starts up with an error. I've just ignored it mostly, but now I'm getting annoyed with it. How can I find the programs that start up every boot to research this, or stop it from loading Interface Builder every time?

You have to delete it using the minus sign at the bottom. The check/un-check is for hiding items.

Looking for simple sample of iphone apps without using Interface Builder

I successfully went through the 'iphone app tutorial' and used Interface Builder, but now want to try creating apps without it.
The UI Catalog sample is too complex, but didn't see anything that just had a view and a button or label.
Ideally I want code that doesn't require any IB usage, but I can't tell if that is possible yet...
Anyone have a link to an easy sample?
Or has anyone created a test app themselves and wouldn't mind posting?
I took a stab at creating one and posted it on the "101" forum, but it would be hard for somebody to try and figure out what I was attempting
Thx for any links/___sbsstatic___/migration-images/migration-img-not-avail.png
ps
I really need a good book, especially "cookbook" style

hey dear
I have one solution of your problem
just go to in iphone developer search for FAQ
In faq their is one section how to use prohramming in this you can see
the how to ceate label,button etc.
after that simply add the view or remove theview.

Cannot open nib - The application Interface Builder quit unexpectedly

Just installed the iPhone SDK and installed sample code. The Interface Builder will not start. At startup, the following message is displayed: "The application Interface Builder quit unexpectedly."
I've tried the standard Xcode SDK and it has the same problem. I've repaired permissions on the disk, to no avail. I'm stumped on this. Thanks for any suggestions.
Here's the first section of the crash report, showing the builds for Interface builder and Mac OS X (10.5.6).
Process: Interface Builder 8090
Path: /Developer/Applications/Interface Builder.app/Contents/MacOS/Interface Builder
Identifier: com.apple.InterfaceBuilder3
Version: 3.1.2 (677)
Build Info: InterfaceBuilder-6770000~1
Code Type: X86 (Native)
Parent Process: launchd 137
Date/Time: 2009-01-03 19:29:24.618 -0700
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000011
Crashed Thread: 0
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x910272b4 CFRetain + 36
1 com.apple.HIToolbox 0x911ff566 TThemeFont::SetCTFont(__CTFont const*) + 62
2 com.apple.HIToolbox 0x911ff4f4 TThemeSpecifiedFont::Init(THIThemeTextInfo const*) + 32
3 com.apple.HIToolbox 0x9110ccb3 ThemeFontCreate(THIThemeTextInfo const*) + 239
4 com.apple.HIToolbox 0x9110cb85 TThemeText::ConstructThemeFontWithFontID(__CFString const*, THIThemeTextInfo const*) + 79
5 com.apple.HIToolbox 0x9110ca49 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 159
6 com.apple.HIToolbox 0x9110c781 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 177
7 com.apple.HIToolbox 0x9110c659 ThemeTextCreate(void const*, THIThemeTextInfo const*) + 33
8 com.apple.HIToolbox 0x9110c3b5 DataEngine::GetTextDimensions(void const*, float, HIThemeTextInfo*, float*, float*, float*) + 289
9 com.apple.HIToolbox 0x9110c250 HIThemeGetTextDimensions + 202
10 com.apple.HIToolbox 0x912abbad HIClockView::CalculateTextDimensions() + 133
11 com.apple.HIToolbox 0x912abd82 HIClockView::GetOptimalSizeSelf(CGSize*, float*) + 118
12 com.apple.HIToolbox 0x9114852d HIView::SendGetOptimalBounds(CGRect*, float*) + 151
13 com.apple.HIToolbox 0x9114846d HIView::GetOptimalSize(CGSize*, float*) + 53
14 com.apple.HIToolbox 0x9119bd85 GetBestControlRect + 105
15 ...terfaceBuilder.CarbonPlugin 0x162f127a IBWindowForHostingCarbonControls + 9638
16 ...terfaceBuilder.CarbonPlugin 0x162f1b1f IBWindowForHostingCarbonControls + 11851
17 ...terfaceBuilder.CarbonPlugin 0x162f2766 IBWindowForHostingCarbonControls + 14994
18 ...terfaceBuilder.CarbonPlugin 0x162f37c8 IBWindowForHostingCarbonControls + 19188
19 ...terfaceBuilder.CarbonPlugin 0x162eb17a 0x162e5000 + 24954
20 com.apple.InterfaceBuilderKit 0x002c65e0 -IBLibraryObjectTemplate classesOfPasteboardObjects + 194
21 com.apple.InterfaceBuilderKit 0x002c64b9 -IBLibraryController typeSummaryForObjectTemplate: + 106
22 com.apple.InterfaceBuilderKit 0x002c5fc4 -IBLibraryController createAssetForTemplate:inNamespace: + 554
23 com.apple.InterfaceBuilderKit 0x002c4fe3 -IBLibraryController createAssetsFromTemplatesInNibNamed:forPlugin: + 746
24 com.apple.InterfaceBuilderKit 0x002c499e -IBLibraryController loadLibraryObjectsForPlugin: + 287
25 com.apple.InterfaceBuilderKit 0x002c414e -IBPlugin didLoad + 480
26 ...terfaceBuilder.CarbonPlugin 0x162ea66f 0x162e5000 + 22127
27 com.apple.InterfaceBuilderKit 0x002c389f -IBPluginController loadPluginAtPath:error: + 2809
28 com.apple.InterfaceBuilder3 0x00002345 0x1000 + 4933
29 com.apple.AppKit 0x91f983a3 -NSApplication run + 83
30 com.apple.AppKit 0x91f658a4 NSApplicationMain + 574
31 com.apple.InterfaceBuilder3 0x00004eca 0x1000 + 16074

Thanks for asking. It happens when I click the "Interface builder.app" name in finder and when I double-click an .xib file name in finder.
As I mentioned, I have repaired permissions on the drive to no avail. I have also read older posts on the web referring to various preference plist files but those don't exist with this build of xcode.
I have also had older builds of xcode on this mbp and worked thru a couple of tutorials. Interface Builder from those older builds worked. I'm not sure were to get them, now, and I doubt they would have the iphone sdk included.

Interface Builder - no Inspector

Similar Messages

Maybe you are looking for