If you need a generalized solution, you can change your generated
methods to do exactly what you want through the template. This would
then give you all the functionality you want in the standard
generated methods.
With EOGenerator, you generate 2 class files. One is a subclass of
the other. This way, you never regenerate the file where your
business logic is, so you don't have to worry about merging after
changing your schema.
Ken
On Oct 11, 2006, at 9:39 AM, Florijan Stamenkovic wrote:
Hi Ken,
How many cases do you need this information in? Personally, I
would use EOGenerator, generate 2 class files (the underscore and
regular classes) and add set and get methods with special names to
the class. Then you could hook up your UI to those methods
instead of the regular methods, and be guaranteed to know when
they change without a lot of extra plumbing.
I was just logging all what comes through takeStoredValue...().
Stupid me, I forgot about the plumbing...
So, it seems that what you an Sacha suggested (implementing through
generated classes) is the only reasonable solution. Although I do
not understand your suggestion. Why are two class files needed?
I understand Sacha's idea about using generated setter methods to
post my notifications, and think it should work, if I change my GUI
code to use only generated setters, and EOCustomObject methods that
attempt to go through them before anything else.
