Hello,
The problem lies in the boxing of the value into a NSNumber. Here is a dirty
way:
NSKeyValueChange changeKind = (NSKeyValueChange)
change[NSKeyValueObservingNSKeyValueChangeKindKey].SendMessage("unsignedIntValue");
Regards, Laurent Etiemble.
2009/2/4 Joanna Carter
> Laurent Etiemble a
Laurent Etiemble a écrit :
Hello,
Change
Id valueId = change[NSKeyValueObserving.NSKeyValueChangeKindKey];
to
NSNumber value =
change[NSKeyValueObserving.NSKeyValueChangeKindKey].CastTo();
Merci Laurent, ça faisait la différence !
But do you have any better ideas on how to avoid a second
Hello,
Change
Id valueId = change[NSKeyValueObserving.NSKeyValueChangeKindKey];
to
NSNumber value =
change[NSKeyValueObserving.NSKeyValueChangeKindKey].CastTo();
Regards, Laurent Etiemble.
2009/2/4 Joanna Carter :
> Laurent Etiemble a écrit :
>
>> What version of Monobjc are you using ? A lot
Laurent Etiemble a écrit :
What version of Monobjc are you using ? A lot of constants have been
fixed in the latest version (2.0.313), and NSKeyValueObserving is part
of the fixes. Tell me if you still have the issue with the 2.0.313.
Thank you Laurent, that fixed that problem.
Now, I just ha
Hello,
What version of Monobjc are you using ? A lot of constants have been
fixed in the latest version (2.0.313), and NSKeyValueObserving is part
of the fixes. Tell me if you still have the issue with the 2.0.313.
Note that the bug tracking system can be accessed at
http://tracker.monobjc.net an
Hi folks
I just wanted to confirm a possible bug in the NSKeyValueObserving class.
Using Reflector to check the initialisation of this class, I see the
following :
static NSKeyValueObserving()
{
NSKeyValueChangeKindKey =
NSString.NSPinnedString("NSKeyValueChangeKindKey");
NSKeyValueChang
6 matches
Mail list logo
