NSButton Key Equivalent bug in Interface Builder 3.1?

We are supposed to be able to "... select the [Momentary Push In] button and open the attributes pane of the inspector. ... click in the Key Equiv. field, and type the key or key combination you want to associate with the button.' In order to associate the Return key with pushing the button.
However, the Key Equiv. field is grayed out and it is only possible to set the key equivalent programmatically with [myButton setKeyEquivalent:@"\r"];
Is this a bug in IB 3.1 and if so how does a person report this bug?

Oops! My mistake. Eventually sussed out how to use the IB "keystroke entry" style of specification - not the most intuitive perhaps. But now I know! Used anywhere else I wonder?

Similar Messages

Interface Builder - Custom images not visible in Cocoa Simulator

I'm very new to this, and just toying around with Interface Builder more than anything at this stage…
Anyway, my problem… I've created some of my own images to place on buttons, etc. I've saved them in PNG format and dragged them into the Resources folder of my Xcode project, so they become available in Interface Builder's media library. I can drag them onto my window just fine, but when I test the UI with the 'Simulate Interface' command, the images disappear completely.
Any ideas?

This was changed in Interface Builder 3.0. Now, you have to click on the "Connections" tab in the object's Info panel. I think it is the 2nd one from the right. You will recognize it because you will see all your outlets. You click the little circle next to the outlet and drag a line over the user interface object to make the connection. Once you do that, there is a bug in Interface Builder that will blank out the info panel. You will have to select some other object to redisplay any information, then click back to your original object. The bindings panel has a similar set of bugs. Suffice to say, Interface Builder 3.0 is a work in progress.
PS - to break a connection, click the little X button next to an outlet name.

Trying to make a NSMatrix (of NSButtons) in Interface Builder 3.0

In Interface Builder 2.x, to make a NSMatrix of NSButtons, all you had to do was option click and drag a corner after the guidelines appear till you had a NSMatrix. For some reason you can't do this anymore with IB 3.0. Does anyone know how to make a NSMatrix of NSButtons?

I found out how. It's not the same, but basically you have more freedom. Just option drag a button, again and again till you have your pseudo NSMatrix built. After this go under Layout, to Embed Objects In ->, to Matrix, with all the buttons selected, then you have a NSMatrix.

Interface Builder ( IB ) font bug?

I noticed in ib, if i choose arial and then bold face (for labels, titles etc) it displays the text properly and is the proper bold. but when i deploy the app the text is gone, what i find wierd is in ib if you choose fonts that are not on iphone the text itself looks like it is the default font (eg. it doesnt let you use none iphone fonts)
so is this a bug with arial bold only?
i also tried to choose regular arial and then on the interface builder top menu i choose font >> bold and it turns the text bold, and it still doesnt display when compiled..
It makes no sense to me to have ib to do interface stuff when something like simple font choosing is buggy and/or not properly supported.

Human interface guidelines mandating a certain degree of consistency in appearance make a lot of sense, as would the fact that you cannot use fonts which are not available on the target system.
Arial is a horrible ripoff of Helvetica anyway.

Interface Builder Bug?

I have a cocoa program that I have I am writing on a 10.6 system, but targeting to 10.5.
On the 10.6 system, it works fine. However, when I run it on the 10.5 machine, I get:
The sender of menu item actions is now the NSMenuItem, not an NSMatrix. A menu item action method appears to be trying to send the NSMatrix method 'accessibilityIsIgnored' to its sender. This is no longer valid. Please change the code.
I looked this up online and found that one place implies that I'm calling "accessibilityIsIgnored" in my code, which I am not, or that there are multiple copies of the InterfaceBuilder library on the system, which there are not.
has anyone else seen this?

Actually, that looks like a very, very old error message. It seems to have been encountered only by you and one other person back in 2003. Do you have some old versions if the interface Builder application? Are you linking some ancient libraries?
Can you reproduce the error in a new, template-based HelloWorld application?

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

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 refuses to see "@2x" image files

I'm making some apps with support for all three major iOS platforms: iPhone&Co, iPhone4 and iPad. This support means, naturally, having larger-resolution images for the latter two platforms. Currently I'm making the apps universal, so the same app will run in all of them.
Since most of the double-resolution images of the iPhone4 version of the app can be used as-is in the iPad version (only things like background images have to be made separately for all three types of platform due to differing screen resolutions; the rest can be done with simply laying out the elements appropriately in the iPad as compared to the iPhone4, using the same element images for both), it would be a huge waste of space to make separate images for the iPhone4 and the iPad, when these images would be completely identical. Thus it only makes sense to reuse the same "@2x" images of the iPhone4 on the iPad version of the app.
This worked nicely for a while. However, at some point quite suddenly (I don't really know what happened), Interface Builder started to completely refuse to see any image files with a "@2x" in their name. It won't show them on the drop-down menu where you select an image (eg. for an UIImageView or UIButton), and if you write it manually, it will refuse to show it (only showing the question mark image symbolizing a missing image file). The image will show ok when running the app, but IB simply refuses to acknowledge the existence of such images. If I rename the image such that I remove the "@2x", then IB will accept it, but not if it has those characters.
As said, IB did see the "@2x" images at some point, but for some reason now it doesn't. (This is a bit of a mystery because I don't remember this happening after any kind of SDK upgrade or anything.)
This tells me that this is either 1) a bug in IB, or 2) intentional behavior, and the "@2x" images should not be "abused" in this way to create an iPad version of the app properly.
If hypothesis 2 is correct, then what is the proper way of using the same images in both the iPhone4 and iPad versions of the app? Duplicating the image files would be an enormous waste of space (the apps are quite graphics-heavy).
One "kludge" that comes to mind would be to create soft links for the images so that the iPad versions of the image files would just be soft links to the @2x iPhone4 images. However, I don't know if the bundling mechanism of the iPhone SDK supports soft links, or if it will simply make copies of the images (in which case each such image will end up being stored twice in the bundle).

WarpRulez wrote:
If I rename the image such that I remove the "@2x", then IB will accept it, but not if it has those characters.
I guess I don't understand why you want a solution when you've found one already.
Just use ".2x" or "-2x" or whatever.
Report the bug, use your workaround and move on.

Interface Builder: Problems with selecting items?

Hello, does someone else have experience with IB selection problems?
I did the following:
-Created a textured window
-Dragged a toolbar into it
-Dragged a NSScrollView into the textured window
-Gave the NSScrollView a white background
-Scaled the NSScrollView so that it extended to the edges of the window
-Dragged 4xCheckboxes into the NSScrollView
After this I had major problems in selecting any of the Checkboxes. It seemed like if I moved the mouse around a bit and kept clicking, then in some point I was able to get the checkbox selected. However this happened only after 5-30 clicks. Also the scaling controls of the checkboxes were almost impossible to find and to use.
Is there a button or a checkbox in the IB configuration, or a keyboard key or something in the IB that would make selecting things a bit easier. Or am I just doing something wrong?

Interface Builder is pretty buggy to begin with, so that is always going to be a hassle. You normally have to double-click inside scroll views to get to the actual contained items. Also, you can drill down through the scroll view in the object window in tree view and select the checkbox itself.

Interface Builder - Locking Properties

Good morning all,
I have some question about the feature to lock properties in Interface builder. I am using Interface Builder 3.0 (629) and I am not sure if the behavior I am seeing is a bug or if it is just some small details I am unaware of. Here is my little annoying problem:
Whenever I open some of my nib files ( they are now all saved as NIB 3.0) some of them instantly are flagged as something changed, and some don't.
1: I can't figure out why Interface Builder thinks that. The only thing I can think of, is that I might have created the Nib file on a primary monitor ( I am developing a Macbook pro) and sometimes I might have created the Nib file on a second monitor. Is it because Interface Builder is relocating the Nib file on the 2nd monitor ( which has the Dock) that he thinks something has changed??
2: Also, when I am trying to lock the nib files using Non-Localizable properties, on some NSTextField it still does not let me edit the text.
3: Whenever some locking is applied, I have the same issue as in (1), Whenever I open up a locked Nib file, I see the big LOCK image flashing. ( I think interface builder is trying to do something) And on some NIB file it is fine.
I also noticed that when my Nib files were saved as Nib 2.0 I could not save the deployment Target OS.
Thanks for confirming my doubt or explaining these undocumented behavior if they are not!
Simon

Nothing beyond what Apple's already released or said in the press releases is known, or can be discussed, by anyone here. Sorry, but we'll all have to wait and see.
As to individuals writing their own apps, again, we'll have to wait and see, but there's no indication that Apple will support this anytime in the foreseeable future. Their emphasis is on providing apps that won't totally screw up an iPhone, so therefore I'd I doubt strongly that Apple's going to want to support iPhone on which any of us can install anything we happen to cook up.
Regards.

Interface Builder fonts?

I'm just starting to figure out Interface Builder/ Xcode, but I've run across either a very bad bug or something I'm missing. Hopefully the latter.
I made a new iOS (iPad) project, opened the .xib file in Interface Builder, and added, among other things, a "Scrolling text view". I can edit the text and change the font size, but any attempt to change the font itself doesn't work. As in, as long as I'm in edit mode (of the text) the font appears to change, but as soon as you click out of edit mode the font changes back to Helvetica. And the iOS Simulator shows Helvetica too. :/ I don't have the Developer Membership yet, so I can't try it out on my iPad, but I assume it would do the same thing.
Is there some switch that needs to be turned on/off? I've googled but haven't found much. Or is it a bug? (a very bad one, if so)

You need to post this in the right forums. Those are the developer's forums at developers.apple.com. You may also try the Developers forum here. But if you wish to be an authorized iOS developer then you need to join the iOS Developers and pay your $99 annual membership fee for registration.

Interface Builder Assertion Failure at initialization/startup

Interface Builder appears to be unusable...
I get four (4) alert messages at the start of running Interface Builder:
====
Interface Builder encountered an internal logic error. Choose "Continue" to continue running Interface Builder in an inconsistent state. Choose "Crash" to halt Interface Builder and file a bug with Crash Reporter. Choosing "Crash" will result in the loss of all unsaved data.
====
Selecting (Show Details) I get:
====
Assertion Message: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
IBUIViewImageRequester failed to rasterize a UILabel, UIButton, UITextField, and UISegmentedControl.
Exception name: NSInternalInconsistencyException
Exception reason: [NOTE: this exception originated in the server.]
Invalid parameter not satisfying: font != nil
Exception backtrace:
0. CoreFoundation 0x30279dfb [NSException initWithName:reason:userInfo:]
1. libobjc.A.dylib 0x92750e3b objcexceptionthrow
2. CoreFoundation 0x3028e5fb CFReadStreamGetBuffer
3. Foundation 0x305b0594 [NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:]
4. UIKit 0x309fe074 [UILabel setFont:]
5. UIKit 0x309fec08 [UILabel _commonInit]
6. UIKit 0x309fd13c [UILabel initWithFrame:]
7. Interface Builder Cocoa Touch Tool 0x00008655 [UIView initWithMarshalledValues:orderedKeys:marshallerClassNames:andMarshallerInstanti ationContexts:globalMarshallingContext:]
8. Interface Builder Cocoa Touch Tool 0x0000b307 [IBCocoaTouchToolObjectPackage dealloc]
9. Interface Builder Cocoa Touch Tool 0x0000b80f [IBCocoaTouchToolObjectPackage initWithData:]
10. Interface Builder Cocoa Touch Tool 0x0000a5a1 [IBCocoaTouchToolObjectPackage dealloc]
11. Interface Builder Cocoa Touch Tool 0x00002c74 [IBCocoaTouchTool produceImageForRequest:]
12. Interface Builder Cocoa Touch Tool 0x00002445 [IBCocoaTouchTool produceImagesForRequests:]
13. CoreFoundation 0x3024a10d CF_forwarding_prep0
14. CoreFoundation 0x30249ff8 [NSInvocation invoke]
15. CoreFoundation 0x3026eaf8 [NSInvocation invokeWithTarget:]
16. CoreFoundation 0x3026e094 [NSDate initWithTimeIntervalSinceNow:]
17. CoreFoundation 0x3024a0a2 CF_forwarding_prep0
18. CoreFoundation 0x3024a10d CF_forwarding_prep0
19. CoreFoundation 0x30249ff8 [NSInvocation invoke]
20. Foundation 0x3053e15d [NSConnection dispatchInvocation:]
21. Foundation 0x3053c307 [NSConnection handleRequest:sequence:]
22. Foundation 0x3053ba13 [NSConnection handlePortCoder:]
23. Foundation 0x3053b5be [NSConcretePortCoder dispatch]
24. Foundation 0x3053ae33 [NSDOStreamData bytes]
25. CoreFoundation 0x30246e79 CFRunLoopRemoveObserver
26. CoreFoundation 0x30245560 CFRunLoopRunSpecific
27. CoreFoundation 0x30244628 CFRunLoopRunInMode
28. Foundation 0x30535525 [NSRunLoop runMode:beforeDate:]
29. Interface Builder Cocoa Touch Tool 0x000020af [IBCocoaTouchTool startServingForPortName:]
30. Interface Builder Cocoa Touch Tool 0x00002e77 [IBCocoaTouchTool produceImageForRequest:]
Exception info:{
Backtrace:
0. Interface Builder 0x00004d29 [IBApplication handleAssertion:inFile:onLine:]
1. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
2. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
3. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
4. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
5. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
6. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
7. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
8. AppKit 0x906e4d0d _DPSNextEvent
9. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
10. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
11. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
12. AppKit 0x9091c069 [NSApplication runModalForWindow:]
13. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
14. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
15. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
16. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
17. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
18. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
19. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
20. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
21. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
22. AppKit 0x906e4d0d _DPSNextEvent
23. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
24. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
25. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
26. AppKit 0x9091c069 [NSApplication runModalForWindow:]
27. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
28. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
29. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
30. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
31. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
32. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
33. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
34. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
35. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
36. AppKit 0x906e4d0d _DPSNextEvent
37. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
38. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
39. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
40. AppKit 0x9091c069 [NSApplication runModalForWindow:]
41. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
42. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
43. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
44. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
45. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
46. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
47. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
48. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
49. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
50. AppKit 0x906e4d0d _DPSNextEvent
51. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
52. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
53. AppKit 0x906dd5fb [NSApplication run]
54. AppKit 0x906aa834 NSApplicationMain
55. Interface Builder 0x00004eca [IBApplication changeInspectorMode:]
====
If I press (Continue) and then try to create any fields which need text, such as a label or button, I get the exact same alert window, and nothing "appears to work" as far as getting past this.
Some background...
I have no problems like this on my PPC development platform, just on my Intel-based system.
Configuration:
Intel hardware, 1.6 Ghz, 2GB, Mac OS/X 10.5.7
Originally I installed the the devtools from: xcode3122621developerdvd.dmg
and the 2.0 or 2.1 iPhone SDK, but never used Interface Builder (long story)
When the final SDK for 3.0 came out, I installed that from:
iphonesdk_3.0_leopard_9m2736final.dmg
A few days ago, I said, OK, enough reading, I'm ready to start on my application, and fired up Xcode, created a new project and double-clicked on the .xib file to build my interface.
That's when I first saw this problem... and now I'm stuck.
What I've done since...
#1) Deleted prefs for Interface Builder (ibtool), and XCode
retried... same error
#2) wiped /developer clean and resinsatlled from iphonesdk_3.0_leopard_9m2736final.dmg
retried... same error
retried #1, retried, same error
#3) ran /Volumes/Olórin/Developer/Library/uninstall-devtools --mode=all
rebooted
checked international to make sure US/English was selected
repaired disk permissions
rebooted
verified, no prefs files in ~/Library/Preferences or /Library/Preferences
retried... same error
HELP!!!

! ! ! - O M G - ! ! !
{quote:title=reststop wrote:}
#3) ran /Volumes/Olórin/Developer/Library/uninstall-devtools --mode=all
{quote}
I was about to post a reply which included the entire crash log for details... and saw this line:
7/21/09 12:44:16 AM [0x0-0x28028].com.apple.InterfaceBuilder3[269] Couldn't read font cache (file://localhost/Volumes/Olo%C3%83%C3%85rin/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0. sdk/System/Library/.lilid/.lili).
The file is there, so why can't it read it... uh oh, not exactly
... I typed /Olórin/ not /Olo%C3%83%C3%83rin/
Apparently somewhere internal to Interface Builder, when it translates characters, it does it TWICE,
so instead of 'ó' (that's 'option-e o', we have 'o%C3%83%C3%83' which may have worked if it had
only been '%C3%83', without the extra o, or the extra %C3%83.
I am so glad I found this, but I'm furious at Apple for making me rebuild my development system 3 times!
...someone really needs to do better QA on a product used by so many users.
I changed the name of my disk from Olórin to Olorin and Interface Builder works fine!
The PROBLEM all along was the name of my development disk ! ! !
Someone at Apple, please NOTE!
Someone please tell me how to report this, and maybe get Apple to hire me even if just for better QA!
-Carl

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!

HT1925 My ipod is not showing up when I have itunes up. I was told to remove itunes and reinstall however. I receive a message with unable to uninstall the Itunes. It states "could not open key HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\INTERFACE\(915DA835-02FE-

can someone please advise on what I should do? unable to uninstall the Itunes. It states "could not open key HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\INTERFACE\(915DA835-02FE-4953-92FA-624BDF5D 85AB) VEIFY THAT YOU HAVE SUFFICIENT ACCESS TO THAT KEY, OR CONTACT YOUR SUPPORT PERSONNEL, Which i did . I contacted the apple support and they could not help. has anyone gotten this error? Did some research some results show that this has occurred during updates on the itunes but has not seen how to successfully uninstall without getting this error. I attempted to use the control panel and uninstall but it provides me with the same error all the time. I NEED SOME Answers on this issue. Can you please help?!

Perhaps try the fixit from the following Microsoft web page. (Try the "problems uninstalling" option.)
Fix problems with programs that can't be installed or uninstalled

NSButton Key Equivalent bug in Interface Builder 3.1?

Similar Messages

Maybe you are looking for