From: Sean L. <se...@da...> - 2005-09-13 16:06:40
|
On 13 Sep 2005, at 17:08, Jonathan Paisley wrote: > Even if the triggerChangeNotifications... method worked, I like the > idea of a ruby meta-method for setting them up - much less to type! Absolutely, and I've made mine more flexible just now so you can say: cocoa_depends_on :key, :dependency cocoa_depends_on [ :key1, :key2 ], :dependency cocoa_depends_on :key, [ :dependency1. :dependency2 ] cocoa_depends_on [ :key1, :key2 ], [ :dependency1, :dependency2 ] (I think on reflection cocoa_depends_on is a little more clear than cocoa_depends) > > There seem to be some differences in behaviour between Panther and > Tiger. I have a vague recollection of having to disable some of my > ruby-level manual change notifications after the move to Tiger, > since exceptions were appearing. What OS version are you using? Tiger 10.4.2 - haven't tried this on Panther. > If you can post your code and any specifics you've identified about > the way RubyCocoa interacts with the Objective C KVO system that > would be great. I'll try to do the same soon with the code I have. I've attached my code. It relies on the property handling stuff in CVS HEAD (unless that's been released now ... ?) |