RE: T5: Event bubbling

2008-09-09 Thread Blower, Andy
> Not sure how this could be expressed in a method name convention, but > that's > > not necessary for this IMHO. > > > > Now I'll wait for Howard to tell me an obvious reason this can't be > done > > that'll make me feel silly... lol > &

Re: T5: Event bubbling

2008-09-09 Thread Howard Lewis Ship
name convention, but that's > not necessary for this IMHO. > > Now I'll wait for Howard to tell me an obvious reason this can't be done > that'll make me feel silly... lol > > Andy. > >> -Original Message- >> From: Blower, Andy >> S

Re: T5: Event bubbling

2008-09-09 Thread Josh Canfield
be done > that'll make me feel silly... lol > > Andy. > > > -Original Message- > > From: Blower, Andy > > Sent: 09 September 2008 11:08 > > To: 'Tapestry users' > > Subject: T5: Event bubbling > > > > I'm trying to handl

RE: T5: Event bubbling

2008-09-09 Thread Blower, Andy
l wait for Howard to tell me an obvious reason this can't be done that'll make me feel silly... lol Andy. > -Original Message- > From: Blower, Andy > Sent: 09 September 2008 11:08 > To: 'Tapestry users' > Subject: T5: Event bubbling > > I'm

T5: Event bubbling

2008-09-09 Thread Blower, Andy
I'm trying to handle an event in a parent component of one that fires the event and it doesn't seem to work unless it's a generic catch all event handler like onAction(). If I specify the component id like onActionFromThing() or specifying component="thing" in an OnEvent annotation it doesn't ca

Re: Re: T5 : Event bubbling

2008-04-10 Thread nille hammer
ff: Re: T5 : Event bubbling Gesendet: Do, 10. Apr 2008 Von: Stephane Decleire<[EMAIL PROTECTED]> > Thanks Armand. > Returning 'this' works great ! > > Stephane > > Francois Armand a écrit : > > Stephane Decleire wrote: > >> correct behavior of eve

Re: T5 : Event bubbling

2008-04-10 Thread Stephane Decleire
Thanks Armand. Returning 'this' works great ! Stephane Francois Armand a écrit : Stephane Decleire wrote: correct behavior of event bubbling in T5 (i mean handlers which returns null values do not catch the event) ? If yes, what is the solution for an handler to both catch the event and show

Re: T5 : Event bubbling

2008-04-10 Thread Francois Armand
Stephane Decleire wrote: correct behavior of event bubbling in T5 (i mean handlers which returns null values do not catch the event) ? If yes, what is the solution for an handler to both catch the event and show the same page to the user ? Returning a non null value is the think to do, see :

T5 : Event bubbling

2008-04-10 Thread Stephane Decleire
Hi, I have several components encompassed in each other : say A encompasses B which encompasses C. When someone trigger an eventlink in C, i try to catch the event in B in a handler like this one : @OnEvent (value="action") Object change() { // ... management of the action ...

Re: T5: Event bubbling

2007-08-31 Thread Josh Canfield
Can you provide a little more information about your setup? How are you delegating to BlockPage? Is it a page or a component? On 8/31/07, Imants Firsts <[EMAIL PROTECTED]> wrote: > > Hi! > > I have a page (MyPage) which displays a form by > delegating the form rendering to a block in a different >

T5: Event bubbling

2007-08-31 Thread Imants Firsts
Hi! I have a page (MyPage) which displays a form by delegating the form rendering to a block in a different page (BlockPage). MyPage renders fine, but when the form is submitted it generates Prepare and Submit events in the BlockPage and they are not propagated back to MyPage. Is there a way to r