Interface Builder - Picker + orientation

Hi all,
I just wanted to know if there is any way to add pickers to an application from Interface Builder, or do these have to be done programatically ?
Also, is there any way to start a nib in interface builder that assumes / forces orientation into landscape when the application is started, as opposed to all applications being started as portrait ?
Thanks...

Thanks, but I'm still struggling to understand the interaction between Interface Builder and iPhone. I've built a xib that contains a UIView that I changed the class of to UIPickerView.
After this, what do I need to do? Looking at the UIPickerView docs, it looks like I need to provide a delegate and a datasource.
I can find examples of implementing the whole thing in code, but how do I do part of it in IB like I've done, and then provide the delegate and the datasource in the code ?
I'm assuming that I need to associate an object / class with the Picker, but I'm not really sure I understand that at all.
Are there any good starter docs out there for building an app in IB and then working with that in Xcode ?
TIA,

Similar Messages

Trying to create first iPhone app, use Interface Builder or Xcode first?

I'm trying to create my first iPhone App, do I start with Interface Builder or Xcode first? And how do I link the two together?

It's not really that simple -- you'll be working with both. Interface Builder is used to design the GUI (graphical user interface, which consists of the windows and buttons and text fields and so forth, the parts of the application that your user interacts with). Xcode, on the other hand, is used to write the code that tells that GUI what it's supposed to do, and how to do it. So, to answer your question as best I can -- generally, I would imagine you would want to start by creating the basic form of your GUI in Interface Builder and then start coding where appropriate in Xcode, then you'll move back and forth between the two (Xcode and Interface Builder) as needed.
If you're new to programming and want to start with iPhone apps, I recommend picking up a book on the topic (Apress publishing has a book called "Beginning iPhone 3 Development: Exploring the iPhone SDK" that is a good one, and don't forget to take advantage of Apple's iOS Dev Center, which has lots of good documentation on most any topic that will be helpful in supplementing the information in the book you buy -- click [here|http://developer.apple.com/iphone/index.action] to go there).
Keep in mind, however, that trying to learn to program iPhone apps will be difficult (to say the least) if you don't already know Objective-C, and the Apress book I recommended above will not be easy to follow without understanding Objective-C first. Objective-C an object-oriented extension of C, and it is the programming language that is used to develop iOS apps (apps for the iPhone, iPod touch, or iPad). I would definitely recommend learning Objective-C on the Mac before jumping in to iPhone development in specific. Apress has another book called "Learn Objective-C on the Mac" that I would recommend for this.
Furthermore, since Objective-C is an extension of C, you won't have an easy time learning it without a prior understanding of the C programming language. Again, Apress has a book for this, called "Learn C on the Mac."
Put simply, learning to program for the iPhone is not something that comes overnight -- it's a step-by-step process that takes patience, and you have to be willing to go through these steps if you want to learn to program properly for the iPhone.
Step 1 -- learn the C programming language
Step 2 -- learn the Objective-C programming language
Step 3 -- apply your knowledge to developing for iOS (iPhone's operating system) with the Cocoa Touch framework
Anyways, that's just my advice -- I definitely recommend taking the time to do it right and not jumping straight into the deep end, but in the end only you know what works best for you. Also, like I said, I definitely think investing in a book on the subject is worth the time and money, so let me know if you want any other recommendations for books beyond the ones listed above.
Hope this was helpful to you, and best of luck with your journey toward programming for iOS.

How to make a form for input in web interface builder

Hi expert:
How to make a form for input in web interface builder?I have already used it to do PS planning, but I don't know how to draw lines and checkboxes . Thanks in advance.
Allen

WAD:
Open the WAD and create a new template. On the left hand navigation you will have several Web Items available. Under 'Standard' you have 'Analysis' item. Pull that into your template to the right. Under the Properties tab you need to pick the query [form/layout] that you have built in Query Designer.
You will also find other items such as Button group, Checkbox, drop down, list box etc available. Pick and drag into the template whatever it is you require. Lets say you want a button. Under the Properties tab select the 'Command' that you require. You could use standard commands that are available there. You could also define functions and commands that you require.
Query Designer:
Open the QD and drag the characteristics and key figures that you require into the rows and columns of the QD. You would need to specify restrictions under the Filter tab of the QD based on the granularity of data that you require. You would need to remember that the key figures need to be made Input Ready [do this by clicking on KF and on the planning tab select "change by user and planning functions"].
This shouldgive you a start. After you've explored it yourself a bit we can discuss further and I can certainly provide you additional details/material on these areas.
Srikant

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

Yet another cocoa without interface builder post

I am sure its been brought up before. I would like to know if its possible to write Cocoa apps without Xcode, Interface Builder, or NIB files in general; another words, write Cocoa programs programmatically using ONLY Objective C. Before you ask me why I would want to do such a thing and that I am crazy, please hear me out.
I come from a Win32 background, and my primary languages are C and C++. I am getting used to Objective C (though I wish I could use C++ to program in Cocoa). I picked up a copy of Cocoa(R) Programming for Mac(R) OS X (3rd Edition) by Aaron Hillegass, and have been trying to learn cocoa from it for the last few months. Basically, I am having big trouble wrapping my mind around cocoa via the very conceptual high level approach this book takes. I can not for the life of me begin to understand this whole making connections with interface builder.
I do NOT plan to write production applications in cocoa by hand, but if I could just write a few trivial applications in cocoa by hand without interface builder or nib files, perhaps when I do use interface builder, I won't have such a hard time understanding whats going on.
Thanks in advance for the help.

__mikem wrote:
I am sure its been brought up before.
I don't care. Your question isn't about learning how to program and learning via the iPhone SDK. I'll do anything I can for you
I would like to know if its possible to write Cocoa apps without Xcode, Interface Builder, or NIB files in general; another words, write Cocoa programs programmatically using ONLY Objective C.
Certainly. You can write command-line Cocoa apps. Xcode is just an IDE like Visual Studio.
Before you ask me why I would want to do such a thing and that I am crazy, please hear me out.
I come from a Win32 background, and my primary languages are C and C++. I am getting used to Objective C (though I wish I could use C++ to program in Cocoa). I picked up a copy of Cocoa(R) Programming for Mac(R) OS X (3rd Edition) by Aaron Hillegass, and have been trying to learn cocoa from it for the last few months. Basically, I am having big trouble wrapping my mind around cocoa via the very conceptual high level approach this book takes. I can not for the life of me begin to understand this whole making connections with interface builder.
You specifically asked to avoid the topic, but I'm sure there are several of us who are really tired of iPhone questions who would be happy to try our hand at explaining the User Interface architecture in Cocoa - if you want to try.
I do NOT plan to write production applications in cocoa by hand, but if I could just write a few trivial applications in cocoa by hand without interface builder or nib files, perhaps when I do use interface builder, I won't have such a hard time understanding whats going on.
You can write Objective-C programs using whatever editor and IDE/makefile you want. You can even work with all the non-UI parts of Cocoa to get a feel of how it works. Technically, you could write code using only Carbon and never use Objective-C, but that is really a dead-end.
A good idea might be start looking at doing writing MacOS X kernel extensions. You should still use Xcode, but only as an IDE. The code would all be C++ (or a subset thereof) with no user interface or NIB files. Realistically, that is probably harder than learning Interface Builder, but it is probably the most productive path available to you for developing MacOS X and avoiding Interface Builder.

Manual coding vs. Interface Builder - iPhone

I have most of an app done with IB and I've managed to get things to work mostly, but I did have a lot of problems with UIDatePicker and could only get it to work properly when creating it manually.
I have some other strange bugs, like the Delete button sometimes animating accross the top of the window rather than on the row it's supposed to and based on my experience with the date picker, I don't know if that's a problem with my code or with using IB.
Also, most of the sample code seems to create things manually.
So, am I better off using Interface Builder for my iPhone apps, or creating everything manually in code? At this point I'm leaning towards doing everything manually.

A lot of the sample code creates elements programmatically because Interface Builder didn't exist early in the beta. Others (like UICatalog) do it to make the view heirarchy more obvious.
I usually recommend using Interface Builder wherever possible. Remember, there's nothing stopping you from altering IB-created views in your viewDidLoad method; just add outlets for the views you need to customize and connect them as needed. In my experience, it's usually easier to move parts of an application away from IB when you need to do so than it is to move them to IB to make them easier to maintain; working with pure code encourages certain design patterns (like not-really-needed view subclasses and custom constructors to avoid repetitive initialization code) that don't really play well with IB.

Organising items in Interface Builder

I have a number of problems with handling container hierarchies and object groups in Interface Builder.
1. If I Group a number of items (say a slider and its labels), this does not mean that I can move the entire group as a unit - I still have to Shift-click all the individual items to get them to move. If I Cut a group, then only the subitems I have selected will be Cut, but if I Copy, then the entire group will be copied. This strikes me as somewhat inconsistent.
2. If I create a Box and create items in it, those items will align with the Box and follow it around if I move the Box. But if I Cut or Copy an item from one Box and then place it in another box, it will not be a subitem of that Box, and will not follow when the Box is moved. I have not been able to find a way to indicate a new parent to a relocated item, is there one?
3. Sometimes I can drag across a box to select subitems in it, sometimes dragging will instead cause the box to move. I have not been able to discern a clear pattern, does anyone know what the preconditions are for selection one way or the other?
4. The on-line manual for Interface Builder is rather superficial and does not cover questions such as these, nor do the books on XCode/Objective C that I've looked in. Is there any document or collection of notes that goes into further details on the functions of Interface Builder?
PowerBook G4 Mac OS X (10.4.7) Interface Builder 2.5.4

Hi Kai,
1. What you mention first is not what I see as far as I can tell - If you have a bunch of controls, drag over to select them all and group them together (⌘G) a dotted line appears and surrounds the group. I cannot move any one member of the group without the whole group moving as well - expected behaviour. However, your observation of cutting and copying seems correct. Perhaps the 'cut' operation should remove the entire group to the clipboard as copy does, leaving the currently witnessed behaviour for the 'delete' key.
2. Yes. Drag it over the box and let go, then click and hold without moving it and you should notice the shading change a little followed by a green plus icon if you then move it. Drop this now and it'll become a subitem of the box. This also works in reverse.
3. Click somewhere outside the box to deselect it. Click somewhere in the box - but not on any of the contents - eight selection dots should appear around it. This is the box itself selected and dragging will now move the whole box and contents (again, don't hit any of the items inside when dragging). Click somewhere outside again to deselect it. Now double click somewhere inside it (not on items) and a sort of blue lined box with tick marks on it should appear - this shows that the inside is selected and dragging will select items in it rather than move the whole thing. This can also be observed by directly clicking on one of the items inside (puts you straight inside it).
4. Not sure, you sort of pick these things up by trial and error and reading posts and such like (very much like some of the more lesser known OS tricks, modifier keys, etc). There may well be a nice collection of tips on the net somewhere but I haven't come across it yet...
IB seems a little flaky on some of this stuff, especially when repeating actions like putting something into a box, then removing it, then putting it back in, etc. Seems it loses the plot somewhere and you have to dump it and grab another one. Same sort of thing with messing about with matrices - often it starts to misbehave. Hopefully all this sort of thing and what others have complained about from time to time are the result of minimal updates to IB over the last couple of years. Here's looking forward to IB 3!

Receiving Open Interface not picking Inter-Org records from Interface

Hi,
I am trying to receive the inter org transfer through the Receiving Open interface, but the interface not picking the data from the interface tables (RCV_HEADERS_INTERFACE, RCV_TRANSACTION_INTERFACE).
I am in 11.5.10.2, all the sources worked fine like Vendor, Internal Order, Customer but the issue is with the Inventory source (inter orgs)
Please could you advise what could be the reason for the interface for not picking the Inventory source data from the interface table.
Below are the interface insert script that am using..
INSERT INTO RCV_HEADERS_INTERFACE
(HEADER_INTERFACE_ID,
GROUP_ID,
PROCESSING_STATUS_CODE,
RECEIPT_SOURCE_CODE,
TRANSACTION_TYPE,
AUTO_TRANSACT_CODE,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
LAST_UPDATE_LOGIN,
CREATION_DATE,
CREATED_BY,
SHIPMENT_NUM,
RECEIPT_HEADER_ID,
SHIP_TO_ORGANIZATION_ID,
EXPECTED_RECEIPT_DATE,
EMPLOYEE_ID,
VALIDATION_FLAG
VALUES
(rcv_headers_interface_s.nextval , --Header_Interface_Id
rcv_interface_groups_s.nextval, --Group_Id
'PENDING', --Processing_Status_Code
'INVENTORY', --Receipt_Source_Code
'RECEIVE', --Transaction_Type
'DELIVER', --Auto_Transact_Code
SYSDATE, --Last_Update_Date
-1, --Last_Updated_By
-1, --Last_Update_Login
SYSDATE, --Creation_Date
-1, --Created_By
'ICR-001', --SHIPMENT_NUM
21073573, --RECEIPT_HEADER_ID
2266, -- SHIP_TO_ORGANIZATION_ID
SYSDATE+1, --Expected_Receipt_Date
5543, --Employee_Id,
'Y' --Validation_Flag
INSERT INTO RCV_TRANSACTIONS_INTERFACE
(INTERFACE_TRANSACTION_ID,
GROUP_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
TRANSACTION_TYPE,
TRANSACTION_DATE,
PROCESSING_STATUS_CODE,
PROCESSING_MODE_CODE,
TRANSACTION_STATUS_CODE,
CATEGORY_ID,
QUANTITY,
UNIT_OF_MEASURE,
ITEM_ID,
AUTO_TRANSACT_CODE,
SHIPMENT_HEADER_ID,
SHIPMENT_LINE_ID,
SHIP_TO_LOCATION_ID,
RECEIPT_SOURCE_CODE,
TO_ORGANIZATION_ID,
DESTINATION_TYPE_CODE,
DELIVER_TO_PERSON_ID,
LOCATION_ID,
DELIVER_TO_LOCATION_ID,
SUBINVENTORY,
LOCATOR_ID,
HEADER_INTERFACE_ID,
VALIDATION_FLAG,
SHIPPED_DATE
--SELECT
VALUES
rcv_transactions_interface_s.nextval, --Interface_Transaction_id
rcv_interface_groups_s.currval, --Group_id
SYSDATE, --Last_update_date
-1, --Last_updated_by
SYSDATE, --Creation_date
-1, --Created_by
-1, --Last_update_login
'RECEIVE', --TRANSACTION_TYPE_RECEIVE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_STATUS_CODE
203, -- CATEGORY_ID
20, --QUANTITY
'EACH', --UNIT_OF_MEASURE
4379131, --ITEM_ID
'DELIVER', --AUTO_TRANSACT_CODE
21073573, --SHIPMENT_HEADER_ID
16566939, --SHIPMENT_LINE_ID
101629781, --SHIP_TO_LOCATION_ID
'INVENTORY', --RECEIPT_SOURCE_CODE
2266, --TO_ORGANIZATION_ID
'INVENTORY', --DESTINATION_TYPE_CODE
13706, --DELIVER_TO_PERSON_ID
101629781, --LOCATION_ID
101629781, --DELIVER_TO_LOCATION_ID
'FG', --SUBINVENTORY
46259, --LOCATOR_ID
rcv_headers_interface_s.currval, --Header_interface_id
'Y', --VALIDATION_FLAG
SYSDATE
Thank you,
Genoo
Edited by: Geno on May 25, 2013 4:54 AM

Any suggestion/advise please!
Thanks,
Genoo

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.

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

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.

Xcode 4.2.1 crashes when using a QCView in Interface Builder

Hi, I have been trying to use a QCView in one of my projects but I get a crash everytime. I tried loading the QuartzComposerChart sample application but if I compile the project I get a crash, it just seems to crash when it wants to but I was able to get it compiled if I didn't click on the .nib file. It seems to be related to interface builder anyway.
Adding a QCView to a new project results in a .xib file not being able to be saved I get this error
The document “MainMenu.xib” could not be autosaved. -[NSConcreteMapTable state]: unrecognized selector sent to instance 0x402d47420
Heres my crash log:
UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[NSKeyValueUndefinedSetter state]: unrecognized selector sent to instance 0x4026f43a0
UserInfo: (null)
Hints: None
Backtrace:
0 0x00007fff8963726a __exceptionPreprocess (in CoreFoundation)
1 0x00007fff83bb2d5e objc_exception_throw (in libobjc.A.dylib)
2 0x00007fff896c34ce -[NSObject doesNotRecognizeSelector:] (in CoreFoundation)
3 0x00007fff89624133 ___forwarding___ (in CoreFoundation)
4 0x00007fff89623f48 _CF_forwarding_prep_0 (in CoreFoundation)
5 0x00007fff88c829b2 _PatchToComposition (in QuartzComposer)
6 0x00007fff88c5bd47 -[QCPatchController encodeWithCoder:] (in QuartzComposer)
7 0x00007fff8a60559d _encodeObject (in Foundation)
8 0x00007fff8dc72814 -[NSNibConnector encodeWithCoder:] (in AppKit)
9 0x00007fff8dc72599 -[NSNibBindingConnector encodeWithCoder:] (in AppKit)
10 0x00007fff8a60559d _encodeObject (in Foundation)
11 0x00007fff8a60678e -[NSKeyedArchiver _encodeArrayOfObjects:forKey:] (in Foundation)
12 0x00007fff8a606e56 -[NSArray(NSArray) encodeWithCoder:] (in Foundation)
13 0x00007fff8a60559d _encodeObject (in Foundation)
14 0x00007fff8dbe5ab7 -[NSIBObjectData encodeWithCoder:] (in AppKit)
15 0x00007fff8a60559d _encodeObject (in Foundation)
16 0x000000010aaf0938 -[IBCocoaDocument compiledKeyedObjectsData:] (in IDEInterfaceBuilderCocoaIntegration)
17 0x000000010aaf10e0 -[IBCocoaDocument fileWrapperOfType:error:] (in IDEInterfaceBuilderCocoaIntegration)
18 0x00007fff8db59801 -[NSDocument writeToURL:ofType:error:] (in AppKit)
19 0x000000010a681231 -[IBDocument writeToURL:ofType:error:] (in IDEInterfaceBuilderKit)
20 0x00007fff8db58769 -[NSDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] (in AppKit)
21 0x000000010a6846ff -[IBDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] (in IDEInterfaceBuilderKit)
22 0x00007fff8db58b68 -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:forceTemporaryDirectory:error:] (in AppKit)
23 0x00007fff8db4285d -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:error:] (in AppKit)
24 0x00007fff8db58911 -[NSDocument writeSafelyToURL:ofType:forSaveOperation:error:] (in AppKit)
25 0x0000000107ad664a -[IDEEditorDocument writeSafelyToURL:ofType:forSaveOperation:error:] (in IDEKit)
26 0x00007fff8db61ea7 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_8 (in AppKit)
27 0x00007fff8db61327 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_14 (in AppKit)
28 0x00007fff8db61c80 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_7 (in AppKit)
29 0x00007fff8a7a5a8d -[NSFileCoordinator(NSPrivate) _invokeAccessor:orDont:thenRelinquishAccessClaimForID:] (in Foundation)
30 0x00007fff8a7a8e65 -[NSFileCoordinator(NSPrivate) _coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] (in Foundation)
31 0x00007fff8db5725c -[NSDocument _fileCoordinator:coordinateReadingContentsAndWritingItemAtURL:byAccessor:] (in AppKit)
32 0x00007fff8db45702 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_1 (in AppKit)
33 0x00007fff8db5ab75 -[NSDocument performAsynchronousFileAccessUsingBlock:] (in AppKit)
34 0x00007fff8db453af -[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in AppKit)
35 0x0000000107b8b66b -[IDEEditorDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in IDEKit)
36 0x000000010a6811fd -[IBDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in IDEInterfaceBuilderKit)
37 0x00007fff8db46d40 __-[NSDocument autosaveWithImplicitCancellability:completionHandler:]_block_invoke_1 (in AppKit)
38 0x00007fff8db40898 -[NSDocument continueFileAccessUsingBlock:] (in AppKit)
39 0x0000000107b898db -[IDEEditorDocument continueFileAccessUsingBlock:] (in IDEKit)
40 0x00007fff8db40cad __-[NSDocument performAsynchronousFileAccessUsingBlock:]_block_invoke_6 (in AppKit)
41 0x00007fff8db71333 __-[NSDocumentController(NSInternal) _onMainThreadInvokeWorker:]_block_invoke_3 (in AppKit)
42 0x00007fff882cc8ba _dispatch_call_block_and_release (in libdispatch.dylib)
43 0x00007fff882ce72a _dispatch_main_queue_callback_4CF (in libdispatch.dylib)
44 0x00007fff895cc4dc __CFRunLoopRun (in CoreFoundation)
45 0x00007fff895cbae6 CFRunLoopRunSpecific (in CoreFoundation)
46 0x00007fff8c1283d3 RunCurrentEventLoopInMode (in HIToolbox)
47 0x00007fff8c12f63d ReceiveNextEventCommon (in HIToolbox)
48 0x00007fff8c12f4ca BlockUntilNextEventMatchingListInMode (in HIToolbox)
49 0x00007fff8d7a23f1 _DPSNextEvent (in AppKit)
50 0x00007fff8d7a1cf5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit)
51 0x00007fff8d79e62d -[NSApplication run] (in AppKit)
52 0x00007fff8da1d80c NSApplicationMain (in AppKit)
53 0x0000000107165eec (in Xcode)
54 0x0000000000000002
This also happens when I try loading a composition into a QCView. Does anyone know how to fix this?
Thanks
Ed

Glad you posted... I am getting similar messages in xcode 4.2.1
The document “MainMenu.xib” could not be saved. -[DVTFileSystemVNode state]: unrecognized selector sent to instance 0x40540f920
I didn't make the connection with QCView until I saw your post. I have several .xib in the project with QCViews and all of them have this same problem. .xib files without QCViews in them are fine.
However, my application does not crash, but runs fine. (The xib's and application were written with xcode 3.2, and I can't edit them now in 4.2.1, because I can't save them. )
Any other clues would be welcome.
Thanks
Keith

How to instantiate a control in code instead of using Interface Builder ?

I really appreciate the combination of the interface builder and Xcode altogether.
However when I am learning QT, I realize I had been pampered by Apple's Design to a certain extend as I only need to create say a NSLabel instance and use Interface Builder to do the linking and never have to worry about instantiating the Object myself.
But I'm curious, what is the way to instantiate a new hmmm say...NSLabel in the code ?
NSLabel* label = new NSLabel();
Then what ?
What you are seeing here is how QT did it, could anyone create an equivalent in ObjC ? No fancy code please, just bare minimum.
#include <QApplication>
#include <QWidget>
#include <QLabel>
int main (int argc, char * argv [ ])
QApplication app(argc, argv); //NSApplication in ObjC
//These two lines merely created a window and set the title bar text.
QWidget* window = new QWidget();
window->setWindowTitle("Hello World");
QLabel* label = new QLabel(window);//Create a label and inform the it belongs to window.
label->setText("Hello World");
window->show();
return app.exec();
Message was edited by: Bracer Jack

Hi Jack -
I think my best answer will be something of a disappointment, because I don't know how to show a one-to-one correspondence between the code you're working with and a Cocoa program. The main function of a Cocoa GUI program for OS X will look something like this:
#import <Cocoa/Cocoa.h>
int main(int argc, char *argv[])
return NSApplicationMain(argc, (const char **) argv);
As you commented, we could draw a correspondence between the first statements, but after that the functionality of the Cocoa program is going to be spread out in a way that makes for a rather tedious comparison. The only way I know to answer your question in less than 5000 words, is to skip ahead to one of several points in the startup sequence where the programmer can intervene with custom code.
For example, a common way to get control would be to program a custom controller class and add an object of that class to the main nib file which is loaded during the startup sequence. By making a connection to the Application object in that nib file, the custom object could be made the delegate of the Application object, and if we then added a method named applicationDidFinishLaunching, our code would run as soon as the application's run loop was started.
Now I finally have enough context to directly answer your question, so here is the code to create a label and add it to the key window at launch time:
// MyAppController.m
#import "AppController.h"
@implementation AppController
- (void)applicationDidFinishLaunching:(NSNotification *)aNotification {
NSLog(@"applicationDidFinishLaunching");
NSRect frameRect = NSMakeRect(150, 300, 150, 30);
NSTextField *label = [[NSTextField alloc] initWithFrame:frameRect];
[label setEditable:NO];
[label setStringValue:@"Hello World!"];
[label setFont:[NSFont labelFontOfSize:20]];
[label setAlignment:NSCenterTextAlignment];
NSView *contentView = [self.window contentView];
[contentView addSubview:label];
@end
If I needed to develop a worst case scenario for this thread, the next question would be, "Ok sure, but your code still needs a nib to start up. I want to see a Cocoa GUI program that doesn't require any nib".
It turns out that it's quite easy to build a simple iPhone app without any nib, but it's considerably more difficult for an OS X app. If anyone wants to see my nib-less iPhone code, I'll be happy to post it (I think I did post it here once before, and the response was underwhelming). But I've never attempted the much more difficult nib-less OS X app. Just in case you really want to go there, here's a blog that goes into the details: [http://lapcatsoftware.com/blog/2007/07/10/working-without-a-nib-part-5-open-re cent-menu>.
Hope some of the above is helpful!
- Ray

Interface Builder Error: Could not read archive

I created a new project in Xcode. I double click on MainWindow.xib and it opens up Interface Builder like it should, but then I get an error saying "Could not read archive". This happens every time with any project I have tried to start; please help.

I' ve the same problem. And if I make a new interface and save it, after a new klick on MainWindow.xib there's tthe error saying too.
Sorry for my bad Englisch, but I'm German.

Interface Builder - Picker + orientation

Similar Messages

Maybe you are looking for