Jump to content

Mithrandir

Members
  • Posts

    3
  • Joined

  • Last visited

    Never

Mithrandir's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Application.LVClass.Open was my first idea, but had also no success Now I've tried your second option, but the vis still keep staying in memory (but no errors from the invoke nodes) i think version numbers in the class name is possible, but only a workaround, and of course the old version will still stay in memory using up space. nevertheless, if updates do not happen frequently this might be an option. thanks for all help
  2. Yes, that's not the problem. I do exactly the same way as you do, but what i wanted to achive is that a plugin can be updated while the rest of the software keeps running. lets say i have a class called ComponentImplementaton that represents my plugin, and i access it throu the class ComponentInterface. further lets asume i have an application that should not be restartet because updates belonging to plugins. the only action should be to reload the plugin but as it seems that is not possible because once a plugin was loaded the class remains in memory. do you know any methods to force the load from disk ( as the Labview IDE can) ? i have attached my testings. Download File:post-1256-1161250951.zip
  3. In our company we are currently working on a pluginsystem for Labview using LVOOP as reference implementation. Now I've found a strange behaviour in the dynamic instanciation process. We call a "create.vi" of the class we want to have by reference and get the interface of it back. We can work with the class normally using the interface, but when all's done an the class was destroyed , the "create.vi" is of course also closed, so nothing of the class is used any more, the "create.vi" of the class still stays in memory. That's a big problem, because we whanted to make the plugins replaceable while the main program is running, which of course can not be done if these vis do not unload. BTW it's not important if i work with the class, the simple call of Open VI Ref let stay the vi in memory even if it was closed again imediatly afterwards any suggestions to solve that problem? PS: My first post in this marvelous forum :beer:
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.