Check for nil — in the set-the-state code add an assertion that _onOffSwitch!=nil, and in -setActive: add an assertion that sender!=nil. That may help track things down.
(Basically, any time I see a weird bug like “I change a property of ___ but it doesn’t do anything” or “a property of ___ is 0/nil but it shouldn’t be”, I immediately start wondering whether ___ is nil.) —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
