Ah...I guess that depends on how something is "conditionally" rendered. If the renderComponent() method gets called on it and Tapestry thinks you want it to get updated it'll happen.
Need more info on how it's being conditionally rendered. On 2/7/07, Daniel Tabuenca <[EMAIL PROTECTED]> wrote:
I'm trying out the new Tapestry 4.1.1 @EventListener annotation and it works great, except that if the event is on a component that is conditionally rendered, it breaks with the following error: FATAL exception raised: bad srcObj for srcFunc: onclick This is understandable since dojo cannot connect the requested event because the element does not exist. Is there a way to deal with this? Or should event listeners not be used with conditionally rendered components? Is there away to conditionally enable/disable EventListeners? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
