> It bubbles up in the ancestor chain until the callback passed to the
> triggerEvent method says the event was handled.
Ah, missed that somehow. That helps returning multiple Zones but
leaves the ancestor problem.
>> Can you be more specific what I should pay attention for? Isn't
>> validation d
On Thu, 23 Sep 2010 11:32:09 -0300, Markus Joschko
wrote:
Eventlink triggers an event in one component that is then bubbling up
the ancestor chain, or?
It bubbles up in the ancestor chain until the callback passed to the
triggerEvent method says the event was handled.
Still only the an
>> Actually, you can reach all the component's ancestor, if you do not
>> return anything in the event handler.
That's not what I want as this is the problem: Only the ancestors.
>> You can use eventlink to hit multiple components, but only one handler
>> can return the final result.
Eventlink t
On Thu, 23 Sep 2010 11:07:13 -0300, Christophe Cordenier
wrote:
Actually, you can reach all the component's ancestor, if you do not
return anything in the event handler.
You can use eventlink to hit multiple components, but only one handler
can return the final result.
see
http://tapestry.
he event and aggregate the result
> in every handler).
>
>>
>>
>> -- Forwarded message ------
>> From: Markus Joschko
>> Date: 2010/9/23
>> Subject: Re: Global events
>> To: Tapestry development
>>
>>
>> Ok, sorry. I tho
--
> From: Markus Joschko
> Date: 2010/9/23
> Subject: Re: Global events
> To: Tapestry development
>
>
> Ok, sorry. I thought the dev list is for questions regarding
> development of tapestry in contrast to questions regarding the usage.
>
> The MultiZoneUpdate i
I would chose to get the list of Zones from the page either by
implementing the event handler in it or by triggering an event from
the component...
-- Forwarded message --
From: Markus Joschko
Date: 2010/9/23
Subject: Re: Global events
To: Tapestry development
Ok, sorry. I
