Skip navigation.
 
mlNSTextField bindings bug - am I going mad?!
FROM : Robert Goldsmith
DATE : Sun Apr 10 21:09:42 2005

Hi all :)

This is driving me mad!

Take the simplest nib you can think of with a binding - 1 square white
NSTextField you can edit, one 'label' style NSTextField you can't edit,
in a window, bound to the same key in an NSObjectController set to
auto-prepare content.

The result should be that when you type stuff into the first field, the
text appears in the second field. Ok?

Right, now make the second field editable and adjust it's binding so
that when the first field is empty, it shows a nice little placeholder
text (enter something in the 'Null placeholder' binding field for the
second field). Now until you type in the first box, you get the
placeholder text in the second box, ok? Now type something so it
appears in the second field.

Then click on the second field.

When I do this, I find the null placeholder renders underneath the
actual content. No idea why, can't work out how to stop it. My only
solution is to not use placeholders (it happens with all of them, it
seems, but it's harder to setup an example to show that) as I want all
my text fields to be selectable so the user can copy-paste.

Is it just me? or is this a bug? Any ideas how to stop it happening?!

Thanks

Robert
---
GnuPG public key:
http://www.Far-Blue.co.uk

Related mailsAuthorDate
mlNSTextField bindings bug - am I going mad?! Robert Goldsmith Apr 10, 21:09
mlRe: NSTextField bindings bug - am I going mad?! mmalcolm crawford Apr 11, 04:53