Follow-up Comment #3, bug #22246 (project gnustep):
I was able to work around the problem with the checkbox being switched off
immediately. It turns out that this was caused by a call to
observeValueForKeyPath:ofObject:change:context: with an empty change
information.
This happens as the same change notification gets send on three levels by
NSKeyValueObserving, after the first one is sent the change info is reset in
didChangeValueForKey: now the next two levels find an empty change info, still
they send it on. I would claim that this is a wrong behaviour and that we
should just not send the notification, when the change has been already reset
to empty.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?22246>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep