What I do as a workaround is store the javascript parameters into form
hidden properties from within my custom javascript function. Since the
EventListener handler posts the form before calling the listener, I can
retrieve the values from there

HTH
Ch.

2007/5/8, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:

I'm now working around this by doing the tapestry.bind directly from my
JavaScript calling the directevent service. Of course, my component now
implements IDirect and the @EventListener annotation is not used
anymore.

Nevertheless, I think passing a stringified version of the intercepted
functions (first) parameter through would be much nicer I think. It
would also provide for some symmetry between native browser events and
custom methods. I don't really want to make you unhappy, however ... ;)

> -----Original Message-----
> From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 08, 2007 12:01 AM
> To: Tapestry users
> Subject: Re: How to pass custom arguments to @EventListener
>
> I've been wary of trying to serialize function parameters as
> that could get very tricky on non simple object structures.
> (json recursion and such)
>
> I guess if they were acceptable to send to the server "as is"
> doing the equivalent of a toString() on them I could add that
> in. (but not be happy about it ;) ) Would that work ?
>
> On 5/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > I'm successfully listening to a custom javacript method
> being called
> > on an element.
> > Now, I'd like to access the argument(s) that were passed to
> this method.
> > Is there an easy way to achieve this? I've looked at the
> BrowserEvent
> > object passed to the listener, but this didn't help.
> > Thanks for any hints,
> >
> > Marcus
> >
>
>
>
> --
> 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]


Reply via email to