Am 13.12.2007 um 21:12 schrieb Fred Kiefer:
I just see that this special case is not
failing there. Should I set breakpoints on methods of the watched
instance and check the back trace for on the fly methods?
Yes, why not?
As for the remaining part, I can't see when the getter method would
Richard Frith-Macdonald wrote:
> On 2007-12-13 17:34:34 + Fred Kiefer <[EMAIL PROTECTED]> wrote:
>
>> While testing key value binding I found a problem with the current KVO
>> code. When an object is starting to get watched a new class gets cooked
>> up to handle the set calls on the object. H
On 2007-12-13 17:34:34 + Fred Kiefer <[EMAIL PROTECTED]> wrote:
While testing key value binding I found a problem with the current KVO
code. When an object is starting to get watched a new class gets
cooked
up to handle the set calls on the object. Here all setter methods get
overridden, w
Fred,
I don't believe you've overlooked anything. What you're describing seems to
me, to be the right behavior.
GJC
--
Gregory Casamento -- Principal Consultant - OLC, Inc
# GNUstep Chief Maintainer
- Original Message
From: Fred Kiefer <[EMAIL PROTECTED]>
To: GNUstep Developer
Sent
While testing key value binding I found a problem with the current KVO
code. When an object is starting to get watched a new class gets cooked
up to handle the set calls on the object. Here all setter methods get
overridden, which is fine, as we don't want to change the class when
another key on th
