• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. How to access the data of a treeStruct (created by hiCreateTree...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 145
  • Views 16676
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to access the data of a treeStruct (created by hiCreateTree) ?

Rein
Rein over 13 years ago

Hi,

     For example,  

                a = hiCreateTree('a)   

 

                b = hiCreateTreeItem(......)   

 

                hiTreeAppendItems(a list(b))

 

How to access data b from a?

I try to use a~>?? to view data of a. But it is display (activeUT hiFieldSym a).


Thanks

Rein

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Laurent,

    Yes, you're right. It should be:

    items=hiGetTreeItems( abTreeExampleForm->shapeTree->choice)

    I had a slightly hacked version of this code in my work area, and for some reason I'd changed the field name to be treeField in my local version and I'd not noticed.

    For your second question, there's two reasons why it doesn't work. First, putpropq is not the same as an array access. It's equivalent (in fact identical to):

    treeField->hiContextMenu=abTreeExampleMenu

    The "q" at the end of putpropq means that the second argument is implicitly quoted - so that means the function is not a normal lambda function in that its arguments are not evaluated before the call - the function itself determines which arguments to evaluate, and which to take literally. It's equivalent (but not identical to):

    putprop(treeField abTreeExampleMenu 'hiContextMenu) ; notice the quote that is necessary if you use putprop rather than putpropq.

    You can use the -> operator (or putpropq) on hash tables, but you can't use the hash table (array access) syntax on forms, form fields, etc. So that's why the [] syntax wouldn't work. If it had have been possible, you'd have had to do:

    treeField['hiContextMenu]=abTreeExampleMenu

    but that won't work because [] is not supported on structures or fields etc.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Laurent,

    Yes, you're right. It should be:

    items=hiGetTreeItems( abTreeExampleForm->shapeTree->choice)

    I had a slightly hacked version of this code in my work area, and for some reason I'd changed the field name to be treeField in my local version and I'd not noticed.

    For your second question, there's two reasons why it doesn't work. First, putpropq is not the same as an array access. It's equivalent (in fact identical to):

    treeField->hiContextMenu=abTreeExampleMenu

    The "q" at the end of putpropq means that the second argument is implicitly quoted - so that means the function is not a normal lambda function in that its arguments are not evaluated before the call - the function itself determines which arguments to evaluate, and which to take literally. It's equivalent (but not identical to):

    putprop(treeField abTreeExampleMenu 'hiContextMenu) ; notice the quote that is necessary if you use putprop rather than putpropq.

    You can use the -> operator (or putpropq) on hash tables, but you can't use the hash table (array access) syntax on forms, form fields, etc. So that's why the [] syntax wouldn't work. If it had have been possible, you'd have had to do:

    treeField['hiContextMenu]=abTreeExampleMenu

    but that won't work because [] is not supported on structures or fields etc.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information