• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Moving to CoreData - List attributes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving to CoreData - List attributes


  • Subject: Re: Moving to CoreData - List attributes
  • From: Lee Morgan <email@hidden>
  • Date: Sun, 15 May 2005 02:16:42 -0400

On May 14, 2005, at 9:29 PM, Lee Morgan wrote:

I'm moving my app over to CoreData and I'm having a little bit of trouble wrapping my head around one part.
In my app I have an array of "Items" (NSDictionary) that each contain a list of "Conditions" (NSString) that correspond to the Conditions Value (NSNumber). In my gui I have it setup so that the items are displayed in a list view with each item having a popup menu for the condition of the item. The user can then choose the condition from this popup menu, and the currently selected condition's value is displayed in a text field cell within the row of the item.
I'm looking for the best way to implement this using CoreData, but I just can't figure out how to do it. I've looked at the OutlineEdit example which is close to what I'm looking for, it displays a list of options, however I can't seem to find a way to change what is displayed in a text field based on what is selected from the list. Is CoreData able to do this?

Disregard. After trying for the past few hours I realized where I was going wrong.
I was using the "option drag" entity ability of xCode / IB to create the GUI for my app, and the GUI it created wasn't working the way I expected... turns out that if you add two entities that reference each other (ie: object1 has a to-many relationship to object2 with reverse lookup) they both create array controllers for object1 - which lead to some strange behavior until I noticed this.


So as I said, disregard my last post.
It's all good.

On a side note the "contentSet" binding ROCKS! And kudos goes to the developer who put in the runtime warning that recommends it over the "contentArray" binding.

- lee
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Moving to CoreData - List attributes
      • From: Kevin Callahan <email@hidden>
References: 
 >Moving to CoreData - List attributes (From: Lee Morgan <email@hidden>)

  • Prev by Date: Re: NSTextView wants to wrap too soon
  • Next by Date: Re: Moving to CoreData - List attributes
  • Previous by thread: Moving to CoreData - List attributes
  • Next by thread: Re: Moving to CoreData - List attributes
  • Index(es):
    • Date
    • Thread