Hi Dragan,
>I have a class defined in a .prg and compiled into an .app, which is then subclassed in a script. I'm creating an object of the parent class just in case, so it's in memory and visible by the subclass. So far so good - this part works.
what's your the use case ? I tried to guess at your needs, and about the only thing I imagined was to overwrite methods so the behaviour in the parentclass is not run - assumptions on nearly no data are unreliable<g>.
For the those cases where the inheritance can't be easisly modified or quasi-MI is needed, I usually go very standard (writing functions with an explitic toObject instead of a hidden this as first parameter) or use wrapper objects sometimes coupled with bindevent, which is great for adding, but tends to become a drag with for stopping functionality via facade and worker objects. Are you creating specialized objects with custom methods drawn from a common base ?
curious
thomas
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only