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
To: GNUstep Developer
Sent: Thursday, December 13, 2007 12:34:34 PM
Subject: Key Value Observation is over reacting
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 ob
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
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
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
Original-Nachricht
> Datum: Fri, 14 Dec 2007 02:11:02 +0100
> Von: Markus Hitter <[EMAIL PROTECTED]>
> An: Fred Kiefer <[EMAIL PROTECTED]>
> CC: GNUstep Developer
> Betreff: Re: Key Value Observation is over reacting
>
> Am 13.12.2007 um 21:
On 2007-12-14 09:37:32 + "Fred Kiefer" <[EMAIL PROTECTED]> wrote:
Original-Nachricht
Datum: Fri, 14 Dec 2007 02:11:02 +0100
Von: Markus Hitter <[EMAIL PROTECTED]>
An: Fred Kiefer <[EMAIL PROTECTED]>
CC: GNUstep Developer
Betreff: Re: K
Datum: Fri, 14 Dec 2007 02:11:02 +0100
Von: Markus Hitter <[EMAIL PROTECTED]>
An: Fred Kiefer <[EMAIL PROTECTED]>
CC: GNUstep Developer
Betreff: Re: Key Value Observation is over reacting
Am 13.12.2007 um 21:12 schrieb Fred Kiefer:
I just see that this special
>
An: Fred Kiefer <[EMAIL PROTECTED]>
CC: GNUstep Developer
Betreff: Re: Key Value Observation is over reacting
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 c
Am 14.12.2007 um 10:37 schrieb Fred Kiefer:
Original-Nachricht
Von: Markus Hitter <[EMAIL PROTECTED]>
I can't see when the getter method would
be used inside KVO at all. Notifications are sent on value changes
only, which does the setter. Where does the conflict arise?
It
Richard Frith-Macdonald wrote:
>
> I have to leave soon (I'm away for the weeked to go to a christmas
> party), so I've comitted the work I've done to svn. I don't expect
> anyone else will be using it so if I've broken KVO that should not cause
> problems (I did make sure my changes compiled).
>
Fred Kiefer wrote:
> Richard Frith-Macdonald wrote:
>> I have to leave soon (I'm away for the weeked to go to a christmas
>> party), so I've comitted the work I've done to svn. I don't expect
>> anyone else will be using it so if I've broken KVO that should not cause
>> problems (I did make sure m
12 matches
Mail list logo
