Hi Florijan,
Am 16.01.2008 um 22:08 schrieb Florijan Stamenkovic:
Sorry for the confusion...
My current setup is to have a common superclass that only provides
the capability to fire events, but does not do it. It requires
subclasses to define setter methods that do fire events.
What I w
Sorry for the confusion...
My current setup is to have a common superclass that only provides
the capability to fire events, but does not do it. It requires
subclasses to define setter methods that do fire events.
What I want is an EOGenericRecord record subclass that will fire
events by
Hi Florijan,
Am 16.01.2008 um 21:08 schrieb Florijan Stamenkovic:
Hi Fabian,
Thanks for the reply. This is (more or less) what I am doing now. I
have a method provided in the common superclass that fires the
event, the only difference from your approach is that I do it after
the change
Hi Fabian,
Thanks for the reply. This is (more or less) what I am doing now. I
have a method provided in the common superclass that fires the event,
the only difference from your approach is that I do it after the
change has occurred. What I wanted to do was get rid of the
EOGenerator /
Hi Florijan,
Am 16.01.2008 um 20:20 schrieb Florijan Stamenkovic:
Hi all,
I've been trying to override some EOCustomObject methods to perform
event firing. However, I bumped into a problem when the objects are
first being initialized with values. The thing is, i use the old
value in the