On Aug 14, 2008, at 11:37 PM, Quincey Morris wrote:
Can you not trigger the update by making the object property (temperature) KVO-dependent on the preference setting? I don't mean the object property's value, just the property itself. Either use keyPathForValuesAffectingTemperature (or whatever) in the class that has the property, if it can get to the preference setting via keypaths, or else call will/didChangeValueForKey:@"temperature" (or whatever) from some controller that monitors the preferences.
That's certainly a possibility but I didn't want to do that because it would bring a lot of view into the model. I guess I don't have much choice, either this or manual updating when the preference changes.
Regards Markus -- __________________________________________ Markus Spoettl
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
