LVOOP Observer

[Eugen_Graf]

Hello LV-developer

I started to learn LVOOP and need some help understanding overriding VIs. Actually I imlemented 4 classes:

Core (dispatcher)
Client (ancestor class for all clients)
Q_Client (inherits from Client calss)
Topic (not really implemented now)

I have problems understanding Override VIs. I implemented a Client Send.vi in class Client. This vi will be overridden from Client Send.vis of each child class. Please look on my imlementation and say me if I right understand it and implemented good/bad.

Thank you, Eugen

P.S. please look at first on Core Start.vi

[Norbert_B]

Eugen,

if you define good implementation as "someone else understands easily what i am doing", i must admit that the project is not too good....
Maybe it is better if you first describe in your own words what you try to achieve. In this description, i want to know why you want to override functions from your parent and what you are doing in your core class (which does not inherit any other class it seems).

From the naming of the cases in your core_start.vi, i asume that you want to compile the application as dll in the end... correct?

Norbert

[Eugen_Graf]

Hello Norbert,here is the explanation (article) I wrote:

http://www.labviewtutorial.eu/en/index.php?option=com_content&view=article&id=51&Itemid=93

Thank you for reply.

Regards, Eugen

Message Edited by Eugen Graf on 07-11-2008 05:21 PM

[Norbert_B]

Eugen,

i cannot tell you, if the approach you are choosing is good or bad in terms of "how fast and easy" you will add LVOOP to your publish/subscriber.
But from taking a second look into your example-project, it looks ok for me.

I hope that you already know about the differences of LV OOP and "traditional OOP". If not, you will definetly be interested in the following links:
LV OOP FAQ
LV OOP: Decisions behind the Design


hope this helps,
Norbert


[Edit] There is some feedback for LV OOP already given to NI esp. for the mechanism of inheritance since it only gives you the possibility to add functionality before and after the inherited code. But i have no information about the status of this in regard of further developement of LV OOP.

Message Edited by Norbert B on 07-14-2008 06:38 AM

Message Edited by Norbert B on 07-14-2008 06:40 AM

[Eugen_Graf]

Thank you 😄