Sure, does "async=true|false" sound like a good parameter name? (It'll only apply when using submitForm)
On 6/28/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
On Wed, 28 Jun 2006 11:42:58 -0400, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > You don't need to do anything at all if you use the EventListener stuff. > Tapestry will do all the hard work under the covers for you. (ie you can > take out that onchange="javascript" stuff ) Time for yet another question. Is there any way to use this annotation and not use asynchronous calls? Or, is there a way to force the page to re-render? I have a component that changes how it appears based on some state that gets changed during the select element's onchange event. Using the old event processing stuff this was a non-issue because a page reload occurred no matter what. I've tried several different ways to force the page to re-render from my listener, but so far, no luck. Thanks, Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
