I modified a dqGOOP class to allow inheritance using data flattened as
string and being placed to the queue following the ideas of my previous
post. It was not a complete dqGOOP class but a fast test that proved
the concept to function correctly with at least a few data types i.e.
strings and I32. The child class also inhereted all the changes in the
data structure of the base class because I placed the base class data
structure typedef inside the child class data structure typedef as the
first member. I didn't get any crashes either. I don't know if I can
post the example here, since according to the dqGOOP license, one
cannot modify the software. Pierre, you can mail me if you want.
Address is tomi dot maila at helsinki dot fi.
LV 8.0 projects are very handy with dqGOOP classes. One can create
class as a labview library (not the same thing as LLB). This
encapsulates a new namespace for the class. Then when one copies the
library, one can make a copy of the class with new namespace. There are
no name collisions because of separate namespaces. A GOOP wizard is not
necessarely needed if one always creates a new class by creating a copy
of the base class library. I didn't get the dqGOOP wizard to function
with LV 8.0, but was easily able to make new classes by duplicating the
containing library using the above mentioned method.
--
Tomi Maila
