Jump to content

Inserting a class cube on a palette?


Recommended Posts

QUOTE (Daklu @ Sep 9 2008, 03:14 PM)

Is there some special technique required to insert a class cube on a custom palette? I've tried several times but it doesn't seem to be working.

The Class Cube is a built-in function and I don't think you can access it. In the palette editor, when selecting "Display path to palette file...", you get a message saying it's built-in.

However, if you create a control and put the class cube in (type def or not), you can insert this wrapper control in any palette or save it to user.lib.

Link to comment

QUOTE (normandinf @ Sep 9 2008, 04:13 PM)

The Class Cube is a built-in function and I don't think you can access it. In the palette editor, when selecting "Display path to palette file...", you get a message saying it's built-in.
That particular cube is for "LabVIEW Object", which is indeed built-in. But for classes in general, you should be able to add to the palette just by selecting the .lvclass file. However, this is not working in LV 8.2, 8.5 or 8.6 (it did work in LV8.2 beta, but broke for some reason in the actual release). No one noticed that until very recently. But the workaround, as has already been mentioned, is easy enough. QUOTE

However, if you create a control and put the class cube in (type def or not), you can insert this wrapper control in any palette or save it to user.lib.

If you want to insert the block diagram constant into the Functions palette, you can create a VI that has nothing except the constant on its diagram and then add it to the palette as a Merge VI.

Link to comment
  • 2 months later...

Along these same lines, how come in my OOP code, my class data is a cube, but on some other code I have inherited, it's a cluster showing the class data? How do I get that later thing?

QUOTE (Aristos Queue @ Sep 9 2008, 05:44 PM)

...If you want to insert the block diagram constant into the Functions palette, you can create a VI that has nothing except the constant on its diagram and then add it to the palette as a Merge VI.

I think you are referring to Place VI Contents. What used to be called Merge is now the deal when you're sopposed to be able to merge two VI's, which is great demo at shows.

Link to comment

QUOTE (BrokenArrow @ Dec 8 2008, 04:38 PM)

Along these same lines, how come in my OOP code, my class data is a cube, but on some other code I have inherited, it's a cluster showing the class data? How do I get that later thing?
There is no cluster view of LabVIEW classes -- the data is private and there is no way to get access to it (including FP access) other than through interfaces the programmer exposes (FP access can be exposed through an XControl if the programmer chooses).

You may have inherited code written with one of the GOOP toolkits, perhaps?

Link to comment

QUOTE (Aristos Queue @ Dec 8 2008, 08:41 PM)

There is no cluster view of LabVIEW classes -- the data is private and there is no way to get access to it (including FP access) other than through interfaces the programmer exposes (FP access can be exposed through an XControl if the programmer chooses).

You may have inherited code written with one of the GOOP toolkits, perhaps?

I bet you're right The originator of the code was a hardcore C++ programmer. It wouldn't surprise me if he used 3rd party OO. I have a good idea... I'll ask him. Sounds radical, I know.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

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