On Apr 7, 2010, at 6:29 AM, Thiago H. de Paula Figueiredo wrote:
> On Wed, 07 Apr 2010 09:34:21 -0300, Pierce T. Wetter III
> wrote:
>
>> 1. What if the eventlink is nested several layers deep in components? Then
>> value has to be passed all the way down...
>
> The context in the Loop wou
On Wed, 07 Apr 2010 09:34:21 -0300, Pierce T. Wetter III
wrote:
1. What if the eventlink is nested several layers deep in components?
Then value has to be passed all the way down...
The context in the Loop wouldn't solve this problem. The context is only
passed from the event that tri
k
> it should also be able to handle it and
> therefore provide the corresponding event
> handler.
>
> g,
> kris
>
>
>
> Von:"Pierce T. Wetter III"
> An: "Tapestry users"
> Datum: 07.04.2010 14:35
> Betreff:Re: Sugge
more or less the same.
if your component creates an eventlink
it should also be able to handle it and
therefore provide the corresponding event
handler.
g,
kris
Von:"Pierce T. Wetter III"
An: "Tapestry users"
Datum: 07.04.2010 14:35
Betreff: Re: Sugges
>>As a new user of tapestry, loop actually bit me because I assumed it did
>> this already and was surprised in my event handlers when my value binding
>> was null.
>>
>
> Why not passing the current object as the context of the EventLink instead?
>
> t:context="value.id">
>
> publ
On Wed, 07 Apr 2010 09:12:10 -0300, Pierce T. Wetter III
wrote:
As a new user of tapestry, loop actually bit me because I assumed it
did this already and was surprised in my event handlers when my value
binding was null.
Why not passing the current object as the context of th
