05-21-2009 04:01 AM
OK, I think I get it with the singleton
I can have a single Check Out VI for the class, and this is what I actually use deep down in my VI hierachy to return the object, which I can then act on the objects (ie call private/public accesso functions). Then when I am done modifying/using the object I have a Check In VI which then effectively allows it to be used again elsewhere.
So no need to wire everything through... this sounds good.
06-15-2012 09:40 AM
Not to rehash an old thread, but I was doing some research and stumbled upon it. I had a lot of similar questions so this thread helped.. Anyway, further research led me to this post
http://lavag.org/topic/11513-singleton-design-pattern/page__p__70428#entry70428
Thought I would share incase people are trying to dive into LVOOP like myself and looking for singleton examples.