Comments on: Extending LabVIEW-built applications with LVOOP plugins http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/ LabVIEW and visual programming blog Wed, 07 Jul 2010 22:34:08 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Tomi Maila http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/comment-page-1/#comment-6872 Tomi Maila Sun, 07 Dec 2008 09:25:27 +0000 http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/#comment-6872 Hi Pierre, Which version of LabVIEW are you using? I'm testing the scenario you suggested with LabVIEW 8.6 and I have no problems. For the Circle plugin, I set both Circle and Ellipse classes as Always Included and voilà, everything works as suggested. I think the the previous versions of the builder may have had problems with colliding classes, so if you are using LV earlier than 8.6, you should consider upgrading. The plugin search algorithm I suggested in the example is pretty plain simple and you should not use this simple version of the plugin search algorithm with your scenario as it will identify all classes used by the plugin class as plugins themselves. Some other indication such as a setting file is needed for identifying the main plugin class. I created a modified example for LabVIEW 8.6 that demonstrates the usage of plugin inheritance. It can be downloaded from the same <a href="http://expressionflow.com/downloads/lvoop-plugins-example/" rel="nofollow">download page</a> as the basic example. Hi Pierre,

Which version of LabVIEW are you using? I’m testing the scenario you suggested with LabVIEW 8.6 and I have no problems. For the Circle plugin, I set both Circle and Ellipse classes as Always Included and voilà, everything works as suggested. I think the the previous versions of the builder may have had problems with colliding classes, so if you are using LV earlier than 8.6, you should consider upgrading.

The plugin search algorithm I suggested in the example is pretty plain simple and you should not use this simple version of the plugin search algorithm with your scenario as it will identify all classes used by the plugin class as plugins themselves. Some other indication such as a setting file is needed for identifying the main plugin class. I created a modified example for LabVIEW 8.6 that demonstrates the usage of plugin inheritance. It can be downloaded from the same download page as the basic example.

]]> By: PierreCottin http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/comment-page-1/#comment-6871 PierreCottin Sat, 06 Dec 2008 23:42:38 +0000 http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/#comment-6871 Very interesting article! I have tried to extend this example to a class Circle inheriting from a class Ellipse. I did not manage to compile the circle plugin to acces both circle and ellipse object. If I do not include the Ellipse class in the projet, it appears as a dependency but the source distribution does not include it. If I include the Ellipse class in the projet, I have to exclude overridden methods and send it to the support directory (to hide it from the main). With two methods, it's not so bad but with a real class hierarchy with several parents, it will be quite complicated. Do you know an easier way to proceed? Thanks. Pierre Very interesting article!
I have tried to extend this example to a class Circle inheriting from a class Ellipse. I did not manage to compile the circle plugin to acces both circle and ellipse object. If I do not include the Ellipse class in the projet, it appears as a dependency but the source distribution does not include it. If I include the Ellipse class in the projet, I have to exclude overridden methods and send it to the support directory (to hide it from the main). With two methods, it’s not so bad but with a real class hierarchy with several parents, it will be quite complicated. Do you know an easier way to proceed?
Thanks.
Pierre

]]> By: Tomi Maila http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/comment-page-1/#comment-2556 Tomi Maila Tue, 03 Jun 2008 12:55:39 +0000 http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/#comment-2556 Ben, nice that you found this article useful. Ben, nice that you found this article useful.

]]> By: Ben http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/comment-page-1/#comment-2552 Ben Mon, 02 Jun 2008 15:50:46 +0000 http://expressionflow.com/2008/06/02/extending-labview-built-applications-with-lvoop-plugins/#comment-2552 Thank you Tomi! A light bulb went on in my head while stuying this example. I had previously missed a very fundamental idea before seeing this example. It had not clciked that the VI I was double clciking on in Main is NOT the VI that executes but rather the Draw.VI of the targt class. Yest the other examples i lloked at must have been doing the same. But 'casue I am an old timer LV coder, I did not realize another VI was beeing slippe dat run-time. Duh! Ben Thank you Tomi!

A light bulb went on in my head while stuying this example.

I had previously missed a very fundamental idea before seeing this example. It had not clciked that the VI I was double clciking on in Main is NOT the VI that executes but rather the Draw.VI of the targt class. Yest the other examples i lloked at must have been doing the same. But ‘casue I am an old timer LV coder, I did not realize another VI was beeing slippe dat run-time.

Duh!

Ben

]]>