Hi Jean,
You might get more feedback from the ZPatterns list on something
like this. My gut reaction is that subclassing in python 2.1/1.5
traverses the classes to find methods in a way that makes the *order* of
classes very important. IIUC Python 2.2 has a much more sophisticated
Thanks Steve,
No doubt that is probably what is happening. Sadly, I need ZClass1 to be
a dataskin. I could always copy over the few properties and methods
shared by ZClass1 and ZCLass2 to ZCLass2 and inherit only from DataSkin
and Folder; not the nicest, but that would work for now. My approach
Jean Lagarde wrote:
Thanks Steve,
No doubt that is probably what is happening. Sadly, I need ZClass1 to be
a dataskin.
Make both ZClass1 and ZClass2 derive from Dataskin before anything else.
It will do no harm that DataSkin is derived from twice in one class.
--
Steve Alexander
It's Steves to the rescue today!
Using the order (DataSkin, Folder, ZClass1) seems to have done the
trick! Thanks!
I would have thought about subclassing DataSkin again, eventually ;-) I
had tried to inherit from (Folder, ZClass1) rather than (ZClass1,
Folder), but that order was giving me a