Jump to content

Create references and use property nodes with grouped controls


Recommended Posts

Hi everyone,

Actually, I've already found the answer to my question in an old thread in which I saw the following picture. Problem is : I can't find how to create a reference to a group of controls and neither can I find the "Grouped" property used below.

The old thread dated from 2006. Was this feature removed in more recent releases of LV or I'm just too dumb to find it? Is there another way to interact with group members?

Thank you!

post-1450-1164184003.jpg

Link to comment

Both of those properties still exist, however they are private. They are amongst my favorite private properties so I can only hope there is a good reason for the privacy.

Read the VI scripting page for the ini key to turn on the private properties, but I would be very hesitant to put them into production code.

Link to comment

They are amongst my favorite private properties so I can only hope there is a good reason for the privacy.

I don't think there's a particularly good reason why these are private. I have filed CAR 380592 and CAR 380593 to see about getting them changed to public in a future LabVIEW version.

  • Like 1
Link to comment

Read the VI scripting page for the ini key to turn on the private properties, but I would be very hesitant to put them into production code.

I have activated the scripting in the options, but I can't find what is that ini key you are talking about and how to activate private properties...

Also, I don't know if this is necessary for my LabVIEW version, but I downloaded the VI package manager and installed the scripting toolkit, but it never showed up in NI license manager so I could activate it...

Further help would be appreciated!!

Thanks

Link to comment

Sorry I was a bit vague there. See this page:

http://labviewwiki.org/LabVIEW_configuration_file/Miscellaneous#SuperPrivateSpecialStuff

Nobody, especially NI, implies any warranty guarantee, expectation for future use, etc. for these private methods. Let common sense be your guide! If (when) your hard drive explodes, you did not hear this from me... :D

That said, have fun, and IMO it is a service to NI for users to identify which of these properties and methods are useful so they can be promoted.

Link to comment

Don't worry! This application is not meant for production but for hardware DVT. I'll be careful I promise ;)

I have written "SuperPrivateSpecialStuff=TRUE" at the end of the "labview.ini" file. Is this the only thing I have to do? Because I didn't see any changes...

Link to comment

Any reason why using the "Grouped" property works in simulation but not when I build the executable?

Most likely since it was added as a quick hack by someone from NI, to be used in a tool, that did not need to run as build executable. The person doing that

1) either didn't think it was useful in a build app

2) wasn't sure there might be certain implications in a build app, that might require extra work for this to work properly

3) made a mistake when adding that property so it does not work properly in a build app

4) or there may have been even some brainstorming and some very bright guys in the LabVIEW developer group identified at least one reason that this feature can't be working as intended in a built app without a lot of extra effort, and so the feature was intentionally disabled for build apps, and that might also be the reason that it was made private, since it is in fact an unfinished feature.

Link to comment

This is common across scripting methods as well. In many cases it is a practical issues that the changes are modifying something that can't be changed post compile. In this case as a read only i guess this doesn't apply but perhaps has simply not been added to runtime due to it being private

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
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.

  • Similar Content

    • By Bruno Costa
      This is the common menu of all group windows. In this menu all variables of group can be selected and displayed on the graph panel, can fix the group on the groups panel, can filter alarms of this group on the alarms panel.
    • By Bruno Costa
      This window is one of many groups windows.
    • By Bruno Costa
      This window is one of many groups windows.
    • By Bruno Costa
      This window is one of many groups windows.
    • By GregFreeman
      I have a tool I'm creating and it searches the active project for all VIs recursively. I have found if I try to use Open VI Reference to an unsaved VI it fails (I am wiring up just the VI name as a string). It gives me error 1004, VI not in memory.
      However, if I go to that specific project and create a new VI and do open VI Reference with "Untitled x" wired as a string, it opens the reference fine. Does the tools menu somehow run in a different context where it can't open a reference to an unsaved VI? Is there a way to make this work?
      I should add, there are no problems when it's saved to disk and wired up as a path (somewhat obviously).
×
×
  • Create New...

Important Information

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