Thank you for your answer!
It isn't gone. Now you have a single EventLink which is rendered once
for each Loop iteration. Static structure, dynamic behavior. ;)
So when I have several components of the same type in my .tml it does a
difference to having a loop? I thought it's just a different way to say
the same thing.
As a consequence, the event "termselect" is always triggered in the
first facetbox instead of the one defining the EventLink.
Use the context parameter of EventLink to identify each rendered link.
Hm, I thought about that. But how does it help me to know which
component should have been triggered when its still the wrong one? If I
would have two facetbox components and I would klick on the second, the
first one would get triggered and get the information that I meant to
trigger the second. But it couldn't do anything with this information as
it can only access its own properties. And so the information stored in
the second facetbox isn't accessible.
Could you please explain how the context parameter would help me? Thank
you for your help :)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
