Re: Binding CoreData Relationship to an NSTableColumn w/ NSPopupButtonCell [Solved?]
Re: Binding CoreData Relationship to an NSTableColumn w/ NSPopupButtonCell [Solved?]
- Subject: Re: Binding CoreData Relationship to an NSTableColumn w/ NSPopupButtonCell [Solved?]
- From: Bill Coleman <email@hidden>
- Date: Tue, 26 Jun 2007 21:05:13 -0400
On Jun 26, 2007, at 12:32 AM, mmalc Crawford wrote:
On Jun 25, 2007, at 8:22 PM, Bill Coleman wrote:
[...]
So, how do I get both -- I want my Entry value to show up in the
table, and all the Selection values to show up in the Popup -- ?
Why does the Insert Null Placeholder modify the display of the table?
You've almost certainly set up a binding incorrectly.
<Sigh> That was my thought, too. However, after exhaustively trying
just about every combination of bindings, I decided to ask a question
on CocoaDev.
Why not just create an "automatic" UI using Interface Builder (drag
the Entry entity into a window)? It should set up the Selection
popup and associated array controller for you...
Well, that certainly was a worthwhile tip!
It looks like this is a bug in either Interface Builder or
NSPopupButtonCell. If I select a type of Pulldown (instead of the
default of Popup) for NSPopupButtonCell, and I uncheck the Inserts
Null Placeholder checkbox for either the content or contentValues
binding for the enclosing NSTableColumn, it exhibits this odd
behavior. An NSPopupButton works correctly.
I've created a sample project that demonstrates this. I'll file a bug
report next.
In the meantime, I'll switch back to using a type of Popup.
Bill Coleman, AA4LR, PP-ASEL Mail: email@hidden
Quote: "Boot, you transistorized tormentor! Boot!"
-- Archibald Asparagus, VeggieTales
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden