• 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: Bound NSTextField displays Selection Placeholder instead of Null Placeholder
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder


  • Subject: Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder
  • From: Quincey Morris <email@hidden>
  • Date: Sun, 30 Dec 2012 20:29:56 -0800

On Dec 30, 2012, at 07:59 , Keary Suska <email@hidden> wrote:

> I am not sure I am experiencing this bug, if I understand you correctly. I can change the binding placeholder string and the bug will show the new changed placeholder string. Changing the text field placeholder string, however, does not appear to have any effect.

If you saw an incorrect placeholder "No selection", I'm saying, then you saw it because Xcode incorrectly put that string the text field Placeholder String at some point in the past. It's got nothing actually to do with a NSController selection, except perhaps in Xcode's fevered imagination.

However, Xcode doesn't do this routinely. It only happened to me the first time I established a binding for text field newly added to the XIB, then never again. It's presumably dependent on the order of things in the XIB and/or the history of what was changed.

> Looks like I am back to setting the binding placeholder for every field <sigh>

AFAIK you always had to do this. The binding placeholder fields in IB are by default *empty* (though in some cases they *display* gray IB placeholder text to indicate what you would put there if you chose to use the fields), so you would have had to go through once entering binding placeholder strings.

Because of the [apparent] field editor bug, you'd be faced with also setting the text field Placeholder string for every field as well. So, yes, to work around the problem this way, you do have to edit every field.

I wonder, though, what happens if you set the placeholder string directly, after the NIB has loaded. It's a property of the text field cell. Maybe you'd need to set it on the text field cell, or maybe you'd need to set it on the field editor cell.
_______________________________________________

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

  • Follow-Ups:
    • Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder
      • From: Keary Suska <email@hidden>
References: 
 >Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder (From: Keary Suska <email@hidden>)
 >Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder (From: Quincey Morris <email@hidden>)
 >Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder (From: Keary Suska <email@hidden>)
 >Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder (From: Quincey Morris <email@hidden>)
 >Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder (From: Keary Suska <email@hidden>)

  • Prev by Date: Re: Binding NSTableView columns to dynamic properties in Core Data?
  • Next by Date: Re: BAse localisation and strings files compatibility with 10.7
  • Previous by thread: Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder
  • Next by thread: Re: Bound NSTextField displays Selection Placeholder instead of Null Placeholder
  • Index(es):
    • Date
    • Thread