Limiting Tree return values

[murraycam]

I have a tree control on a form populated automatically from a set.

set.external_record_content_get("levels", "alltrim(level1->Level1desc) + \".\" + alltrim(level2->Level2desc) + \".\" + alltrim(level3->Level3desc) ","","",var->mlevel)

I want to use the tree return value as a value to filter records. As you select progressive levels of the tree then the criteria for the search is proggresively narrowed.
How do I get the return value of a tree control to restrict itself to the current level Highlighted and not include the child record values. I can achive this by restricting how deep the tree displays with "var->mlevel" but I would prefer to see all tree levels.
ie.
The tree is showing as follows and Book2 is Highlighted in the tree, but the return value is Book2.Chapter1.Page1 instead of just Book2 which I want
Book1
[Book2]
..........Chapter1
......................Page1
......................Page2
..........Chapter2
Book3

Cheers
Murray

[MikeC]

Re: Limiting Tree return values

Murray,
I am not totally certain, but do believe it is an inherent problem. An xDialog Tree has the capability you need/want however.

I will search a bit more as I want to verify as well whether memory serves on if it can be accomplished via a form's tree control or not....or others may chime in to eliminate my having to do this....

[murraycam]

Re: Limiting Tree return values

You are right Mike it works good in xDialog. Would be good to have it embedded in a form somehow.

dim shared node
dim data1
data1 = set.external_record_content_get("levels", "alltrim(level1->Level1desc) + \".\" + alltrim(level2->Level2desc) + \".\" + alltrim(level3->Level3desc) ","","",0)
result=ui_dlg_box("Simple Tree",<<%dlg%
{ysize=2}
[%S=BLR%.32,10node^<data1] |
<OK>;
[.32node]
%dlg% )

[Tim Kiebert]

Re: Limiting Tree return values

Murray,

As Mike has mentioned there is a difference in behaviour between a form tree control and an xdialog tree control. The form version as you have found will always return the full path of the current choice, wether that choice is at the beginning or the end. (unless you specify a different return value, explained further down)

The xdialog version returns the path only up to the choice made. So
Book2 would return Book2
Chapter1 would return Book2.Chapter1
Page1 would return Book2.Chapter1.Page1
You can then use character functions to extract the last value in the result and count the words in the result to determine the level. There are other ways to handle getting values in an xdialog tree but lets get back to the form version.

EDIT: I was writing this answer a bit at a time this afternoon and see now you have tried the xdialog

The data that is displayed in the tree has one line for each endpoint or leaf.
So the data in your example will look like
Book1..
Book2.Chapter1.Page1
Book2.Chapter1.Page2
Book2.Chapter2.
Book3..

The result returned is the first line that contains the item you clicked on. Choosing Chapter1 will return the second line and choosing Chapter2 will return the fourth.
So obviously what we get out is going to be determined by what we put in. Change the tree data to this

Book1
Book2
Book2.Chapter1
Book2.Chapter1.Page1
Book2.Chapter1.Page2
Book2.Chapter2
Book3

Now when you choose Book2 you get Book2 and choosing Chapter1 you get Book2.Chapter1


You can also specify a different return for each line by adding a �|� and a value like:
Book2.Chapter1.Page1|Page1
This will return Page1. But again no matter which level you choose.

If we now combine the expanded data and the alternate value

Book1|Book1
Book2|Book2
Book2.Chapter1|Chapter1
Book2.Chapter1.Page1|Page1
Book2.Chapter1.Page2|Page2
Book2.Chapter2|Chapter1
Book3|Book3
when you chose Chapter1 the return will be Chapter1.

The next question is how to get your expression to format the data that that goes in to the tree so you can get the correct result out of the tree.

In the attached sample
Tree 1 uses your original expression. (without the level variable)
Tree 2 uses you original expression with alternate result value added
Tree 3 uses user defined values
Tree 4 uses function TreeData() and the list property is set in the form�s OnInit - this behaves like the xdialog
Tree 5 uses function TreeData2() and the list property is set in the form�s OnInit
Tree 6 uses an expression which is converted from function Treedata2()

These examples are based on what I guessed your set might be like and are meant to demonstrate the concepts rather than be excactly what you need. If you still have trouble post a sample of what you have so we can give more specific help.

[murraycam]

Re: Limiting Tree return values

Thanks Tim
I get exactly what you mean. :D
You have explaned it beautifully and I appreciate the Zip file with the examples. I am new to Alpha and although I can understand the logic and thought processes involved it can be a bit slow getting a good enough handle on syntex and functions needed to put some routines togeather.

Much appreciated
Cheers
Murray

[G Gabriel]

Re: Limiting Tree return values

Discussed here
and here.

[gmeredith17]

Re: Limiting Tree return values

Just wanted to say thank you to Tim for his mini tutorial and example in this thread. Something like this should be added to the help file how to section.