Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 13727
  • 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

Is it possible to add checkbox into hiCreateTreeItem?

MedAn

We can specify the description as a list of one or more strings, symbols, integers, or floating-point numbers, but maybe have an opportunity to add check box? Maybe need to write some delegate or something else?

Maybe somebody recommend another way, in general I want to have following functional:

We have tree of checks, and can select which checks will be use, for example

checks

  |

  ------ check1  Y

  ------ check2 Y

  ------ check3  N

where check - it's our treeItems, and Y/N - it's check boxs.

  • No, this is not possible with the hi.*Tree functionality. The only way would be to have some textual description of the Y/N status and then either toggle it via a context menu over the item, or have a checkbox field separate from the tree which gets updated to reflect the status of the selected item (and when you toggle that checkbox it updates the selected item in the tree).

    Regards,

    Andrew.

  • Ok, thx. a lot.

    Could you pls. answer me on the one more question?
    In the documentation we have description on the function like this: hiCreateVerticalBoxLayout, but in dfII this function is undefined.
    How can I use it? And do they look like on the QT?

  • Presumably you're reading the IC617 documentation but not actually using IC617 (maybe you're using IC616)? You'd need to be using IC617 to use this function. These functions were added (and documented) in IC617. They are effectively SKILL implementations of the QVBoxLayout Qt functionality (which you can see info on in the Qt documentation) - although of course they have an "hi" flavour to them.

    Andrew.

  • Andrew,

    I see this kind of GUI in VoltusFi results browser. Is it hidden from end users?

    -Ramakrishnan

  • Thx. again. It's my mistake, I really use 6.1.6 фnd did not pay attention on the version of the documentation.

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.