Property node of the add item in tree

As the attached screen, may I know the syntax of the input parameter of 'Parent Tag'.
It seems sometime it works, sometime not. Any suggestion, thanks. 
Attachments:
ss.png ‏50 KB

Parent Tag Unique tag of the item under which you want to add the new
item. The default is an empty string, which adds the item to the highest level
in the hierarchy.
Child Position Sets where to place the new item in relation to the item
whose tag you wire to Parent Tag. Wire a value of 0 (default) to place the new item directly under the
parent item. Wire a value of 1 to place the new
item under the first child item, a value of 2 to
place the new item under the second child item, and so on. Wire a value of –1 to place the new item under the last child item. If
the value you wire to this input is greater than the number of child items under
the parent item, the method places the new item under the last child
item.
Left Cell String Text to display in the leftmost cell for the new item. The
default is an empty string.
Child Text Array of strings to display in the remaining cells for the
new item. The default is an array of empty strings.
Child Tag Unique tag for the new item. The default is the string you
wire to Left Cell String. If an existing tag
already uses that string, LabVIEW appends a number to the string to create a
unique tag for the new item. You cannot
create a tag that begins with TREE_. All tags that
begin with TREE_ are reserved for use by LabVIEW.
If the tag you wire to the method begins with TREE_, LabVIEW prepends an underscore (_) to create a valid tag for the new item. If the tag you
wire to the method begins or ends with white space, LabVIEW removes the white
space.
Child Only? If TRUE, you cannot indent other items under the new item.
The default is FALSE. This property is similar to the Child-Only Item item on the
shortcut menu of a tree control.
I do not understand your first question Alex.  I'm sorry
Kind regards,
- Bjorn -
Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's
LabVIEW 5.1 - LabVIEW 2012

Similar Messages

  • What is the criteria for showing items in the Add items LOV for MDS?

    I am trying to create an MDS. When I try to add the Item I (that is enabled in this Org), I do not see the item in the LOV. Any idea what setup needs to be done that I might be missing?

    case closed.
    The problem was that I had not set the item to be an inventory item. After checking the inventory item checkbox, I am able to add the item to MDS.
    So, this is another requirement (in addition to the planning method). Thanks for your help Kevin and Ricardo.

  • Displaying leaf nodes at the bottom of a tree that has parent nodes

    I have a problem in that - leaf nodes added to the tree at the bottom appear with big spaces (vertically) between them. It looks as if the nodes are somehow expanded by default!
    Is this a known issue with leaf nodes that are added in below parent nodes?
    I notice in the normal hierarchy the leaf nodes are displayed fine. Also if I return false on isleaf() it displays the last 3 nodes as expandable icons but they're still lage gaps between them.
    this is an example of what i'm getting
    Main �
    +Parent Node(expandable)
    |
    +Parent Node(expandable)
    |
    +Parent Node(expandable)
    |
    |
    |_leaf node (not expandable)
    |
    |
    |_leaf node (not expandable)
    |
    |
    |_leaf node (not expandable)

    You got my interest with your topic subject as I'm working on a library which simplifies the development with Swing trees. However everyone here except you knows nothing about your "anormal hierarchy" which creates you problem.
    Denis Krukovsky
    http://sourceforge.net/projects/dotuseful/

  • Error 1055 occurred at Property Node, only the FIRST TIME I run the VI

    hi !
    I'm managing some object properties with 2 subVIs,
    so I send to the first one a number and a cluster which contains the objects references, so that it controls the "visible" property depending on the number,
    and I send to the second one the previous cluster and an other cluster which contain the objects data, so that it controls the data depending on some parameters.
    VI is better than explaination, so find it attached !
    at the first time you'll run it, the error occurs, so click "stop" button, and run it again, no error, and you'll understand the way it works.
    To fond the error again, just close it completely and re-open it.
    (I built an example VI as close as possible to my real VI, and I get the same error, so I attached only the example)
    hope you'll understand (if no I can explain better)
    thanks a lot.
    Attachments:
    tests erreurs.zip ‏57 KB

    yoz'st wrote:
    smercurio_fc a écrit :
    You have to write to the control/indicator the local variable points to.
    sorry but I don't really understand this... (I'm french).
    A local variable points to a control or indicator. To "initialize" it you have to write a value to it. Or, you can set the value of the control/indicator to a default value.
    I tried to use globals, but the same error occurs...
    Of course it will. Because you're not understanding that you have a race condition. http://en.wikipedia.org/wiki/Race_condition

  • Revoving Xterm from the ADD ITEM TO MENU??

    Now I cannot remove the Xterm from the Workspace Menu. How can I do that?? I even deleted it from the Customize Workspace Menu and its still there in the menu.
    How can I achieve this please??

    if your release is high enough, you could try this BAPI_OUTB_DELIVERY_CREATENOREF.
    Unfortunatley, our release (4.6C) is not so am looking for a bapi/fm that will allow us create a delivery without reference. Did you find one?

  • When i change the value of a combo box using a property node it displays the value not the item label

    I am using a combo box as a select list for text serial commands.  I have items like "engineering", "GUI", and "Scan" for the commands "MDE", "MDN", and MDS respectively which i have input as the corresponding value in the combo box.  so for example the label "engineering" has the value "MDE" in the combo box items list.  when the Vi starts it needs to read the current value MDE, MDN, or MDS and then i want it to display on the front panel the item text corresponding to that command value.
    To do this i have tried to read the serial command, ie MDS and then wire that to a "value" property of a property node of the combo-box, but instead of displaying the corresponding item label, "Scan", it displays the value "MDS" on the front panel instead.  i want the front panel to use the label text when choosing and displaying but the block diagram to use the serial commands.  Can this be done with a combo box?  I'm trying to use a combo box so i can keep it all text and avoid having to build a case statement to convert enums or rings from a numerical value to the text command.
    The correct text value is wired to the value property and it does exist in the combo-box.  I have unchecked "values match items" and selected to not allow undefined values.

    Don't use the value property node.  Use the Text.Text property node.  When creating the property node, select Text, then in the next pop-up box, select Text.
    - tbob
    Inventor of the WORM Global

  • Add Intellisense support to the property node

     
    I really hate having to dig through a long hierarchy of menus when I know what I want:
    Visual Studio (and other MS and non-MS products) have a feature called Intellisense, which is meant to make this easier. Basically, as you type, it pops up a list of matching objects, based on context, so you can quickly select what you want:
    It would be nice if LV had a similar feature - click on a property in the property node using the text tool (or Ctrl+click if using the auto-tool) and now you can type in the property name and you will get an Intellisense-like pop-up, which will have all the relevant properties.
    Specific features it could have:
    It should know all the relevant names - full names with the hierarchy (Boolean Text.Font.Color), long names (Mechanical Action) and short names (MechAction). This could probably be similar to how Quick Drop handles shortcuts or they could simply appear as separate items.
    It should be context sensitive. If the class is Boolean, then there's no need to have Listbox properties in the list.
    It should match all the properties which include the search string (so "in" on a boolean would match both "Indicator" and "Strings[]") and only them.
    It should have the ability to use caps for acronyms (e.g. in the above screenshot you could use "BT" instead of "Boolean Text", similar to what appears in this video).
    It could probably also work on the invoke node, although there it's less needed.
    It could probably also be used to quickly select a class if you have a class specifier using the same basic mechanism.
    This example (LV 2009) shows how useful this could be. You don't need anything installed. Just run the VI and start changing properties.
    Caveats:
    It will only work on the last property in the node.
    It doesn't have the proper list of names and it doesn't implement all the features in the idea, as this is just a basic example.
    Note - this is similar to this idea, but I think that it's much more usable. Also note that the second idea refers to a QDKS which ships with 2010, but that is far from perfect.

    Here's a more detailed response.
    Browser:
    Click Ctrl+Shift+B.
    Get a new window. Great. Just lost a little bit of focus on what I was doing.
    Find the search button. Oh, there it is. It's that little button.
    Oh, another window popped up. What did I want? ...   ...   ... Ah, yes. It was that property.
    Search for it. OK, that was easy. Now Enter.
    Oh, I'm back to the original browser window, but the property is highlighted.
    OK, so now I can drag the property into the BD and get a new property node with that property, but that's not actually what I wanted. I wanted to set a property on an existing node.
    So, to summarize: A key combo, some mouse activity, 3 window changes and we still didn't get what we want.
    Compare that to:
    Ctrl+Click on the property you want to replace.
    Start typing.
    The intellisense popup appears as part of the current window, already navigable with the up and down keys.
    Press Enter.
    And two additional points:
    Imagine working in VS without intellisense. What if you had to use something similar to the browser (or the menu hierarchy) every single time you wanted to get a property?
    You encourage people to work with LV classes. Property nodes offer a productivity enhancement when working with classes and this offers another one, so you not only not be questioning it. You should be evangalizing it.
    And for those who survived this far, a bonus. This example (LV 2009) shows how useful this could be. You don't need anything installed. Just run the VI and start changing properties.
    Caveats:
    It will only work on the last property in the node.
    It doesn't have the proper list of names and it doesn't implement all the features in the idea, as this is just a basic example.

  • Just checking on another odd feature: Typedef enum Property Node "Value" not reflecting changes in the Typedef?

    Just encountered this odd behavior in LV 2011 which I reduced to the following example:
    - create a new VI and drop an enum control on te FP.
    - make this control a typedef and open the corresponding typedef
    - create a "case 1" item and a "case 2" item
    - save the typedef (I used the name Typedef Control 1) and CLOSE it (this is to allow updating of the original control).
    - drop a case structure on the diagram and connect the enum to it:
    So far so good. Now create a "Value" Property node for the enum and use it instead of the terminal:
    If I now go back to the typedef and add a "case 3" item, save the typedef and close it, the control is updated, but the Property node is not.
    How do I know that? For one, the Case Structure contextual menu does not offer to create a case for every value. Also, if I add a "case 3" case manually, it turns red.
    Luckily, the magic Ctrl-R key stroke actually does solve this problem.
    Tested in LV 2011.

    By Ctrl-R trick do you simply mean running the VI?  That is one way to force a recompile, but if you hold down Ctrl while pressing the run button you can recompile without running.  This should not be "dangerous" in any situation.
    As you have drawn your example, I see no reason not to use a local in that situation (ok, maybe for vanity).  Still, I view the behavior you describe as a bug, and it should certainly be fixed for the benefit of local haters out there.  You have to be a little careful where you draw the line between what gets handled in real time and what gets handled only at compile time.

  • Tree Control Property Node for Accessing "Child Text" String Array

    When adding items to a tree control using the EditTreeItems invoke nodes, the inputs include "Child Tag", "Item Indent", "Child Only?", "Glyph Index", "Child Text", and "Left Cell String" as can be seen in this screenshot.
    There are property nodes for the tree control for accessing each of these elements, except for the "Child Text", which is an array of strings. It is possible to access this data as outlined in this forum post, but this method is somewhat involved and round about. 
    I suggest that a property for the Tree class be created to access the Child Text array directly.

     The work around only works if you do not have an empty string element some where in the middle.
    At lest could the "Active Celltring Property" read return an error when you have gone beyond the end of the array.

  • Why the VI starts breaking when I enter property nodes?

    Hi,
    I'm a student in engeneering and need to do a work in labview. It's a Signal generator with in-built osciloscope.
    The VI was working fine ultil I add the property nodes to change wavegraph scales and the VI start breaking with them.
    Can anyone see my VI and tell me why does it happen?
    I send the VI below.
    Best regards
    Ricardo Ferreira
    Solved!
    Go to Solution.
    Attachments:
    PROJECTO_FINAL.vi ‏212 KB

    The VI is not broken and can run.
    However, your axes are set to auto scale so the property nodes for the axes and auto scale are constantly fighting each other.
    LabVIEW Champion . Do more with less code and in less time .

  • Why is the first value missing in the Chart when I use Property Nodes to clear my Charts programatically ?

    Hello everybody,
    I am using Property Nodes to clear my Charts right at the beginning of the program. The Property Nodes (History) are outside a While-loop.
    When I connect a Chart with the counter-variable "i" inside a While-loop, the first point I see in the Chart is (0,1) instead of (0,0). It looks like the Chart misses the first point !
    If the Chart is outside the While-loop the Chart displays all points.
    Can anyone please explain this behaviour ? How can I solve this problem ?
    Thanks,
    Cesar

    Make sure you have the error output from the property node connected to
    the loop border. Even if the error os not used in the loop, this will
    ensure that the property node clears the chart before the loop starts
    running.
    What is probably happening is the loop start running at the same time
    the chart is being cleared, so the first point is also being cleared.
    Ed
    Message Edited by Ed Dickens on 04-11-2006 09:50 AM
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
    Attachments:
    Clear chart before loop.gif ‏4 KB

  • How to customize the default add item in a content area

    Hi!! I want to know what can I do to introduce a file in a content area, but I don't want to use the default page that portal use. I want to customize the add item option, the same that I have done with the folders. The problem that I have is that I need the user to have the file on his/her pc, and the api add_item needs the file on unix, where de DB is installed.
    If anyone has any idea, please help me.

    Hi All,
    Thanks for all your reply, but maybe i didn't describe my problem clear. My problem for the combobox is that once the combobox has a selected value, then there is no way to clear it in the UI even I remove all the items in its ValidValues. From the user interface, the selected value still stays there but actually this combobox is empty and does not have any items. My question is how can I remove the current selected item in the combobox.
    Thanks,
    Lan

  • How to set property nodes for each of the multiple y-axes?

    In Labview 6i, I have set up multiple y-axes on an xy graph. I want to change certain properties of each of the 2 y-axes independently. I believe I can do this using "property node".
    However, after I have created a property node for the xy graph, I realised that there is only 1 y-axis selectable from the list of properties. How can I set the property of the other y-axis then?
    Thanks for the help!

    I believe there is a property called "active graph"... this allows you to
    select the active graph to apply the property changes to...
    Later...
    meng118230 wrote in message
    news:[email protected]..
    > In Labview 6i, I have set up multiple y-axes on an xy graph. I want to
    > change certain properties of each of the 2 y-axes independently. I
    > believe I can do this using "property node".
    >
    > However, after I have created a property node for the xy graph, I
    > realised that there is only 1 y-axis selectable from the list of
    > properties. How can I set the property of the other y-axis then?
    >
    > Thanks for the help!

  • Problem with the Value property node (MacOS)

    As far as I have tested it, Value Property nodes (and Value (signaling)) don't work in MacOS : The value property appears as a boolean, the value(signaling) as a cluster (width, height).
    Even with boolean controls, the node is not working.
    No such problem in LV 8.6.
    Am-I missing something ? Is that some "intended use"  ? Or simply a bug ?
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        
    Solved!
    Go to Solution.

    That sounds like some sort of indexing problem with the property nodes like somesort of corrupted installation.  What if you just delete the property node and recreate it?
    I dropped a numeric control and looked at the shortcut menu for the list of property nodes.  Right below Value and Value (signalling) are Visible (which would be a boolean) and Xcontrol, which when you step down through the submenus, the first choice is Container bounds, a cluster of Width and Height.  So these 2 datatypes that are 2 lower on the list match the ones you are getting.
    What happens if you pick another property node a few elements up or down on the shortcut menu?  Does is happen for some other properties, and if so, are thereany properties that are okay?
    Here is what my property nodes look like for a numeric and I draggged the box up and down to show the natural order of the property nodes.  Note that I have scripting installed, so there are a few more property nodes (and the blue box at the top) that you might not have.
    PS.  Check you signature.  The Kudos button is now moved to the left since the forum upgrade. 
    Attachments:
    Example_VI_BD.png ‏4 KB

  • Help comparing the value of a button using the Property Node (I get a variant)

    Dear Sirs:
    (I'm using LabView 6. I guess the solution is different for 6.1)
    Currently I have created an array of Boolean RefNums (which point to many, many buttons). When I need to know when any (and which) of the buttons was pressed I just compare every element on the array with the constant TRUE. It fact, as the array is built from RefNums, I should compare the VALUE from the Property Node.
    The problem here is that the Property Node for this type of Boolean is a LV Variant, and I need to compare this with a TRUE/FALSE value.
    I tried to convert the TRUE constant to a LV variant and visc. But nothing works... I always get that none of the buttons was pressed.
    Here it co
    mes the question: "How can I compare the value of a Property Node for a Boolean (Button) with a TRUE (or False) constant?"
    BTW, maybe I should explain why I'm using RefNums instead of the direct values: As my project requires tons of buttons, I would preffer using RefNums to refer to them. (I.E. I could use a single VI that takes the RefNum and formats the button to hide it for certain users).
    I have enclosed a VI that contains what I've achieved until now, which is nothing
    I appreciate your time and help.
    Best regards,
    JAVIER VIDAL
    Attachments:
    Other_Main_Menu.vi ‏103 KB

    Javier,
    There is another problem in your code: the booleans are not polled by the main loop so they will remain false until the user presses them again. This renders the boolean latch action useless.
    What you can do is to change the mechanical action of the booleans to non-latch. When you detect a "true" in the polling loop, set the boolean to false again. One added benefit is that once all boolean are non-latch, the value property won't be a variant but a boolean so conversion is no longer needed.
    LabVIEW, C'est LabVIEW

Maybe you are looking for