LabVIEW classes are how you create new data types in LabVIEW. But part of being a new LV data type is having a front panel representation. Although users can write XControls for displaying their classes, and they can put those XControls in the palettes, whenever a user of their class chooses "Create Control" or "Create Indicator" for the LabVIEW class terminal, they get the cube display. In order to really add a new data type to LabVIEW that behaves as well as, for example, the Timestampp or the Waveform, there needs to be some way to associate a class with an XControl and say, "This particular XControl should be used as this class' default control/indicator whenever one needs to be built." (To prevent infinite recursion and load dependency problems, whenever you did Create Control/Indicator on a member VI of the class, users would still get the cube control/indicator.)
But if the XControl is a member of the class and uses even one VI of the class, doesn't this result in the XControl locking the Class locking the Xcontrol locking......?
[cross posted to LAVA]
Is this related to how the new plots are implemented in 2009?
Are the FP Objects here, associated with a default class (or in this case an array of classes)?
Or is this totally different?
I made some comments on LAVA that I want to record here also. The text in italics is from LAVA users.
Daklu, on 08 August 2009 - 11:57 PM, said:
Paul_at_Lowell, on 11 August 2009 - 01:18 PM, said:
Mark Yedinak, on 11 August 2009 - 01:56 PM, said:
jgcode, on 14 August 2009 - 08:44 PM, said:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.