Well actually my fix was wrong. Try / Finally doesn't take into
consideration the case where the button ID is changed in the Ajax
request. I noticed how it's actually being done, and found out that
boolean ajax variable in AjaxSubmit wasn't setting up properly. So then
the dojo.event.connect() calls would get bound to window.onload instead
of the request.
So, that's fixed in the demo. I'm still having some bugs with AjaxSubmit
for more complex cases (maybe when the refreshed button is inside the
refresh area?). I still have to isolate that bug.
Now, I was thinking, when you have several components with the same
Tapestry id in a form (contained in a for, or in several components of
the same kind in a page) it's not a very good idea to do an
updateComponents on one of them. You actually have to refresh the whole
batch of components. Or else... you take the risk that their HTML ids
get changed (since Tapestry just enumerates it sequentally), having your
onclick() events bound to the wrong button. Nasty!!
That's a trickier problem, I think. How are we going to solve it?
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
