• 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: NSString bindings are one-way in Xcode 3.0
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSString bindings are one-way in Xcode 3.0


  • Subject: Re: NSString bindings are one-way in Xcode 3.0
  • From: Bob Smith <email@hidden>
  • Date: Tue, 06 Nov 2007 18:08:10 -0500


On Nov 6, 2007, at 11:27 AM, Daniel Hazelbaker wrote:

I don't know why XCode 3.0 / IB 3.0 would cause this problem, but I have seen this when you type text in a bound textfield (or view) and then click your "OK/Save/etc." button without moving the focus off the text field first.  I don't know if you are having the same problem, but the way I have always solved it in the past (probably not the correct way) is to set the text field/view to "Continuously Updates Value" in the binding.

Daniel Hazelbaker

On Nov 6, 2007, at 7:33 AM, Bob Smith wrote:

An application that I've been working on since Xcode 1.0 makes extensive use of NSStrings to hold and save data.  I've incorporated bindings of many NSStrings to NSTextViews; in Xcode 2.(most recent) all was well.  When I compile and run in Xcode 3.0, the bindings operate in only one direction:  if the NSString is changed programatically, the change appears as expected in the interface; however if the change is made in the Text View, the change is not transmitted to the application's container NSString.

Since 10/27 I'm unable to figure this out.

Bob Smith
email@hidden


I've finally gotten to this paragraph in the documentation:

NSObjectController:  Manages any single NSObject instance. Use this controller to manage a single custom object and its properties. When configuring the attributes for this controller, the Class Name field (in the attributes pane of the inspector) should contain the class of the object being managed.

I have always left the default NSMutableDictionary; Xcode 2.(all of them) didn't fuss and they gave me what I expected.  Now that I entered the various class names, the bindings are complete.  Problem solved.

Bob
email@hidden


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

This email sent to email@hidden

  • Follow-Ups:
    • Re: NSString bindings are one-way in Xcode 3.0
      • From: Chris Hanson <email@hidden>
References: 
 >NSString bindings are one-way in Xcode 3.0 (From: Bob Smith <email@hidden>)
 >Re: NSString bindings are one-way in Xcode 3.0 (From: Daniel Hazelbaker <email@hidden>)

  • Prev by Date: Re: (no subject)
  • Next by Date: Re: Xcode 3 not switching subproject executables
  • Previous by thread: Re: NSString bindings are one-way in Xcode 3.0
  • Next by thread: Re: NSString bindings are one-way in Xcode 3.0
  • Index(es):
    • Date
    • Thread