Re: Simple Event Propagation Problem

2010-10-08 Thread Thiago H. de Paula Figueiredo
On Fri, 08 Oct 2010 05:18:30 -0300, aertsko wrote: This is exactly what I am looking for. Could you explain in more detail how the capturing and triggering of the edit event works? I can capture the action event from my actionlink, but I can't find how to trigger the edit event. @Inject Co

Re: Simple Event Propagation Problem

2010-10-08 Thread aertsko
age in context: http://tapestry.1045711.n5.nabble.com/Simple-Event-Propagation-Problem-tp2433285p3204228.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry

Re: Simple Event Propagation Problem

2010-03-17 Thread Nicolas Bouillon
Thank you Howard for the clear response. Of course it works well now. I was a bit surprised that it doesn't worked because I had already done this kind of event propagation for a method named "onSuccess()". But I believed it worked because I had not specified the name of the component. On Tue, 16

Re: Simple Event Propagation Problem

2010-03-16 Thread Howard Lewis Ship
Because the "action" event was not caught by it's immediate container (the Layout component), it propagated up with a new origin: the Layout component itself. so onActionFromLayout() would work (because the id 'layout' will have been autoassigned by Tapestry). The concept here is that the Layout

Simple Event Propagation Problem

2010-03-16 Thread Nicolas Bouillon
Hi, I have a simple problem. I use a component as a layout, and i want to have an action link that will be handled by the page that use the layout. I believed that the event from actionLink goes from the Layout Component to my page containing the component (here it is Index) Here is the sour