EDAboard.com | EDAboard.de | EDAboard.co.uk | WTWH Media

Tree Table: how to create and reference tree items dynamical

Ask a question - edaboard.com

elektroda.net NewsGroups Forum Index - Cadence - Tree Table: how to create and reference tree items dynamical

Frank Steinmetzger
Guest

Thu May 31, 2012 9:33 am   



Hello again

Unfortunately, this week has been a week of encountering SKILL constraints.
I designed an app form with a tree table which shows a list of commits from
my versioning repository. Upon a click, I would like to show some details
about the commit.

The code examples in the documentation on how to create a tree table all use
manually defined variables (such as dow=hiCreateTreeItem(),
nasdaq=hiCreateTreeItem()). But what if I don't know how many variables I
need? I tried the C++/Qt approach by simply using the same variable for all
items. In semi-pseudo-code (b/c I don't remember the exact names and syntax
of the functions):

nextcommit = getNextCommitInformation() ;own function, returns string or nil
unless( stringp(nextcommit)
item=hiCreateTreeItem( <<information from nextcommit>> )
hiAppendTreeItem( tree item )
nextcommit=getNextCommitInformation()
)

But now of course, when I select an item in the table and my callback is
triggered, I always get the symbol nextcommit as reference, so I can only
reach the data that is stored in the last item of the table. The same
happens when I use hiTreeTableGetSelection(). My SKILL-Savvy Tutor also
doesn't know how to accomplish what I need.

Can you please point me into the right direction? I'd appreciate it.


PS.: How can I get rid of the root line in the tree table? The list is flat
and has no expandable items, so I don't need the line. In Qt it's just one
style setting, but the SKILL equivalent has so far eluded me, and I saw it
possible in some screenshot of the Cadence documentation.
--
Gruß | Greetings | Qapla'

They say that memory is the second thing to go...
I forgot what the first thing was.


Guest

Tue Feb 14, 2017 12:55 pm   



On Thursday, May 31, 2012 at 11:33:01 AM UTC+2, Frank Steinmetzger wrote:
Quote:
Hello again

Unfortunately, this week has been a week of encountering SKILL constraints.
I designed an app form with a tree table which shows a list of commits from
my versioning repository. Upon a click, I would like to show some details
about the commit.

The code examples in the documentation on how to create a tree table all use
manually defined variables (such as dow=hiCreateTreeItem(),
nasdaq=hiCreateTreeItem()). But what if I don't know how many variables I
need? I tried the C++/Qt approach by simply using the same variable for all
items. In semi-pseudo-code (b/c I don't remember the exact names and syntax
of the functions):

nextcommit = getNextCommitInformation() ;own function, returns string or nil
unless( stringp(nextcommit)
item=hiCreateTreeItem( <<information from nextcommit>> )
hiAppendTreeItem( tree item )
nextcommit=getNextCommitInformation()
)

But now of course, when I select an item in the table and my callback is
triggered, I always get the symbol nextcommit as reference, so I can only
reach the data that is stored in the last item of the table. The same
happens when I use hiTreeTableGetSelection(). My SKILL-Savvy Tutor also
doesn't know how to accomplish what I need.

Can you please point me into the right direction? I'd appreciate it.


PS.: How can I get rid of the root line in the tree table? The list is flat
and has no expandable items, so I don't need the line. In Qt it's just one
style setting, but the SKILL equivalent has so far eluded me, and I saw it
possible in some screenshot of the Cadence documentation.
--
Gruß | Greetings | Qapla'

They say that memory is the second thing to go...
I forgot what the first thing was.


Same issue that I'm dealing with now, any solutions?


Guest

Tue Feb 14, 2017 1:32 pm   



On Tuesday, February 14, 2017 at 11:56:00 AM UTC+1, flashm...@gmail.com wrote:
Quote:
On Thursday, May 31, 2012 at 11:33:01 AM UTC+2, Frank Steinmetzger wrote:
Hello again

Unfortunately, this week has been a week of encountering SKILL constraints.
I designed an app form with a tree table which shows a list of commits from
my versioning repository. Upon a click, I would like to show some details
about the commit.

The code examples in the documentation on how to create a tree table all use
manually defined variables (such as dow=hiCreateTreeItem(),
nasdaq=hiCreateTreeItem()). But what if I don't know how many variables I
need? I tried the C++/Qt approach by simply using the same variable for all
items. In semi-pseudo-code (b/c I don't remember the exact names and syntax
of the functions):

nextcommit = getNextCommitInformation() ;own function, returns string or nil
unless( stringp(nextcommit)
item=hiCreateTreeItem( <<information from nextcommit>> )
hiAppendTreeItem( tree item )
nextcommit=getNextCommitInformation()
)

But now of course, when I select an item in the table and my callback is
triggered, I always get the symbol nextcommit as reference, so I can only
reach the data that is stored in the last item of the table. The same
happens when I use hiTreeTableGetSelection(). My SKILL-Savvy Tutor also
doesn't know how to accomplish what I need.

Can you please point me into the right direction? I'd appreciate it.


PS.: How can I get rid of the root line in the tree table? The list is flat
and has no expandable items, so I don't need the line. In Qt it's just one
style setting, but the SKILL equivalent has so far eluded me, and I saw it
possible in some screenshot of the Cadence documentation.
--
Gruß | Greetings | Qapla'

They say that memory is the second thing to go...
I forgot what the first thing was.

Same issue that I'm dealing with now, any solutions?


Just found the solution, try gensym() function to create a unique symbol

elektroda.net NewsGroups Forum Index - Cadence - Tree Table: how to create and reference tree items dynamical

Ask a question - edaboard.com

Arabic version Bulgarian version Catalan version Czech version Danish version German version Greek version English version Spanish version Finnish version French version Hindi version Croatian version Indonesian version Italian version Hebrew version Japanese version Korean version Lithuanian version Latvian version Dutch version Norwegian version Polish version Portuguese version Romanian version Russian version Slovak version Slovenian version Serbian version Swedish version Tagalog version Ukrainian version Vietnamese version Chinese version Turkish version
EDAboard.com map