• 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: CoreData Tutorial bindings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData Tutorial bindings


  • Subject: Re: CoreData Tutorial bindings
  • From: Boyd Collier <email@hidden>
  • Date: Thu, 28 Jul 2005 22:07:13 -0700

Thanks for the feedback. As a matter of fact, after sending my question, I realized that the employee ID text field shouldn't be altered and when I looked at the "bind" check box in its inspector, it was checked. I have no recollection of having done this (but then, neither do I remember lots of other things that I should!). Anyway, the problem has been solved.

Boyd


On Jul 27, 2005, at 7:01 PM, mmalcolm crawford wrote:


On Jul 27, 2005, at 6:36 PM, Boyd Collier wrote:


When the user interface is automatically created by Interface Builder following the instructions in the tutorial, 3 array controllers are created, two of which are for employees. When I used the NSTextFieldInspector for "Employee ID:" in the interface, it was bound to Employee Array Controller 2 (NSArrayController) rather than Employee Array Controller (NSArrayController). Changing this to Employee Array Controller (NSArrayController), that is, to the other NSArrayController that was automatically created, fixed the problem.
Question: Is there something in the tutorial that I missed, or is the tutorial deficient in not making explicit which NSArrayController Employee ID is supposed to be bound to? Or is the step I missed so obvious that someone more experienced with Cocoa would be expected to know it and therefore it was left out of the tutorial?



The tutorial does not require that the employee ID text field be altered. Interface Builder creates the user interface automatically, and I can't offhand think of any reason why it should make an erroneous connection as you describe. What happens if you remove the existing user interface elements and the controllers, and recreate the UI from scratch (as described in <http://developer.apple.com/documentation/Cocoa/Conceptual/ NSPersistentDocumentTutorial/02_CreatingProj/ chapter_3_section_4.html>)?


mmalc

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


This email sent to email@hidden



_______________________________________________ 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
References: 
 >CoreData Tutorial bindings (From: Boyd Collier <email@hidden>)
 >Re: CoreData Tutorial bindings (From: mmalcolm crawford <email@hidden>)

  • Prev by Date: [Core Data - Newbie] Custom validation method called twice.
  • Next by Date: NSTreeController ChildKeyPath
  • Previous by thread: Re: CoreData Tutorial bindings
  • Next by thread: Double Click in NSTableView
  • Index(es):
    • Date
    • Thread