tree's inexplicable loss of form

Im probably missing something very obvious but in my definition I am trying to cull a series of branches from a list but in the process the tree is losing its structure, which I need to preserve. I'm not sure I've ever had this problem or maybe it's just that I never noticed it before. I have attached a screengrab showing the list before during and after the operation...

any ideas?

Attachments:

treeissue.jpg, 511 KB

Replies to This Discussion

Permalink Reply by Pep Tornabell on March 16, 2010 at 10:37am

I think its due to the parameter viewer filter, meaning that if you go input the parameter viewer the information is undestood as "string". You have to input the real data (coming from the cull patern)

Another thing its if you want to work with the path information (you can cull it, you con work it as a list of data, but allways as string.

Hope it was clear enough..

PeP

Permalink Reply by Gabriel on March 16, 2010 at 10:50am

thanks. yeah i just figured it out...I needed to graft my booleans and work on the list itself rather than the list of strings of the paths

Permalink Reply by Pep Tornabell on March 16, 2010 at 11:10am

that's it, but using parameter viewer to extract path information, is something very usefull... also mixed with concatenation operations for strings... but I'm practising this now.. still learning...

Permalink Reply by taz on March 16, 2010 at 4:28pm

Yeah, you got it.

Selecting multiple branches with [Tree Branch] gets you the branches but all the path names are reset to 0 to n-1 integer path names.

RSS