If you use the getClientId() method of your button (assuming you are using a
Tapestry based button component) it will always return the correct client
side id depending on the context you calling it from.
On 9/16/06, Josh Joy <[EMAIL PROTECTED]> wrote:
Thanks Jesse.
I wasn't aware of such a call, though it does seem
what I need to use. I
think I understand what you are saying, though I'm not
sure of the
correct syntax I need to use. I have a for loop that
generates multiple
forms and inside these multiple forms is a button. The
only problem I
have is how in the example below to pass in the button
id, since the
button id is dependent on which iteration of the for
loop it is
(basically the id name is partly made up of the
current iterator of the
for loop).
I tried to google, though am probably am not searching
for the right
approach.
Thanks,
Josh
Jesse Kuhnert wrote:
> Sure. dojo.event.connect("before", dojo.byId("your
button id"),
> "onclick",
> function(event){
> // do stuff
> });
>
> On 9/16/06, Josh Joy <[EMAIL PROTECTED]> wrote:
>>
>> Hi All,
>>
>> Question about forms...I would like to have a
button
>> that has an onClick
>> event that calls a javascript function and I would
>> like to also set up a
>> tapestry listener for the same button, so when the
>> user pushes the
>> button first the onClick function is called, next
the
>> Tapestry listener
>> is invoked. Is such a thing possible?
>>
>> Thanks in advance,
>> Josh
>>
>>
---------------------------------------------------------------------
>> To unsubscribe, e-mail:
[EMAIL PROTECTED]
>> For additional commands, e-mail:
[EMAIL PROTECTED]
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
