Re: Bindings: personName.length can't handle changing personName
Re: Bindings: personName.length can't handle changing personName
- Subject: Re: Bindings: personName.length can't handle changing personName
- From: Allan Odgaard <email@hidden>
- Date: Sun, 6 Jun 2004 17:31:44 +0200
On 6. Jun 2004, at 15:06, email@hidden wrote:
What should I do to make the personName.length to work properly
without having to add any code?
Unfortunately what you experience is a bug in the framework. More
exactly the problem is that adding an observer to a Core
Foundation-bridged class instance will render that instance very
unstable (sending selected methods to the class cause endless
recursion, most likely caused by both having the Core Foundation
bridging and the automatic observer notification mechanism manipulate
the isa pointers and/or class structures -- who said "clever use of the
runtime system"? ;) ).
What makes it more tricky is, that NSString is a class cluster, and
only some of the subclasses are Core Foundation bridged.
The only solution I have found is to write a wrapper for NSString, for
which bindings will then work normally -- but that's generally
unacceptable since strings often come from external sources.
Though please do file a bug report about it, as that will hopefully
make it more noticeable on the Radar :)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.