MenuNodeGetProperty(hNode, iField) - Possible bug or mismatch with Help File?

Hi,

I'm getting some return values that do not match what's stated in the help file for Function : MenuNodeGetProperty(hNode, iField)

Field values:


7 Comment gives me the "Display Name" field not "Comment" field.

8 Cluster -Display correct

9 Equipment -Display correct

13 Target Page -Display correct

101 Returns both "Page" and Content" separated with a comma, i.e 'MyPage, My_FP' it does not display the Custom 1 field content.

Does anyone get the same results? 

Rune

Parents
  • Hi Rune,

    I am going to take a guess that you are calling this function on the workspace equipment model (tree) nodes ?
    What you have listed matches identically with how we load your equipment model up and store it in a menu structure.
    See _Equipment_LoadTask in SA_Include\EquipmentModel.ci and look for the labels beginning with MENU_PROP_. (The include project now has labels for all of those props so you don't have to remember the numbers)

    The "menu system" in Citect is quite a useful beast as it allows us to store hierarchical structures and use the fields as we wish. When we load the equipment model up and store it in a menu tree for fast access, we place the 'display name' in the comment field. The tree has the ability to dynamically switch between equipment name and its display name.
    We also load all the content associated with equipment's configuration into the Custom 1 field.

    cheers,

    bradley
Reply
  • Hi Rune,

    I am going to take a guess that you are calling this function on the workspace equipment model (tree) nodes ?
    What you have listed matches identically with how we load your equipment model up and store it in a menu structure.
    See _Equipment_LoadTask in SA_Include\EquipmentModel.ci and look for the labels beginning with MENU_PROP_. (The include project now has labels for all of those props so you don't have to remember the numbers)

    The "menu system" in Citect is quite a useful beast as it allows us to store hierarchical structures and use the fields as we wish. When we load the equipment model up and store it in a menu tree for fast access, we place the 'display name' in the comment field. The tree has the ability to dynamically switch between equipment name and its display name.
    We also load all the content associated with equipment's configuration into the Custom 1 field.

    cheers,

    bradley
Children
No Data