That's precisely what Howard's nested else parameter is designed to address.
A prettier way to do it would be nice. Context might be possible since T5
templates must be well formed. Or maybe an optional component id reference:
<t:comp id="if1" type="If" test="condition">
...
</t:comp>
...
<t:comp type="Else" testid="if1">
...
</t:comp>
Cheers,
Nick.
Numa Schmeder wrote:
<if>
<for>
<if>
doSomething
</if>
<else>
doSomethingElse
</else>
</for>
</if>
<else> <--------- How do you store this evaluation, it might
evaluate to the value of the last if in the loop!
doSomthingElseElse
</else>
I don't know if I am very clear with this example. The evaluation of a
condition must be stored relatively to a context (component's context or
page's context) and not globally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
