11-03-2011 11:12 AM
Greetings!
I'm working on a project where I am trying to utilize some LVOOP magic. My code is still a mess and unpostable, so I will try and keep this post direct and to the point.
My Class tree is farily simply. A parent class holds all of the needed VIs to override and some basic common data information. Each child class needs its own User Interface in order to function because each will have its own set of controls. These controls manipulate the internal parameters of the object, and when the common "Generate.vi" is called it outputs some text that the rest of my program then uses to complete the operation.
My thought was I could make a "User Interface.vi" and "Get User Interface.vi" as override in my parrent class. The children versions of these files would then contain the needed user interface, and the Get User Interface.vi would pass the reference to the User Interface.vi which would then be passed to the Sub Panel and used to get the final values from the User Interface.vi when the user clicks the "Generate" button in the User Interface.vi.
Does this seem like a resonable approach?
Solved! Go to Solution.
11-03-2011 12:25 PM
I'm not sure I understand what you want, but this might be relevant -
Also, follow the links there to see some more relevant info.
Note that generally it is argued that classes should not export UIs because you may want to have different UIs (localization, different options, etc.).
11-03-2011 12:51 PM
Thanks for the links tst!
"Note that generally it is argued that classes should not export UIs because you may want to have different UIs (localization, different options, etc.)."
I understand, but what if the classes are specifically for the modularization of the UI?
11-03-2011 12:57 PM
Your post on that first link is actually very similar to what I'm trying to accomplish. Thanks!
11-03-2011 03:43 PM
Sweet. Got it working for my project. LVOOP is so awesome.