Also need to create support for nested form buttons. I've hacked in an index retriever to get indexed form buttons working, but i'd like to support keys also. It means recursively searching the parameter names enumeration but it doesn't seem that heavy yet (probably need to look at the size of forms and such like).
Mark
On 7 Jul 2004, at 03:32, Rick Reumann wrote:
Axel Groß wrote:
aaargh. Just found another problem. Seems that the IE is so clever that
if there are multiple buttons of the same name he just
submits the first button of the name, regardless of which of them had been
clicked.
Ok, I think I'll just forget about LookupDispatchAction and HTML 4.0
Sorry for the late reply on this..
Yes give up on the crappy LookupDispatchAction (but not the regular DispatchAction). I've used the LookupDispatchAction for a long time and it ends up becoming way more of a pain than it's worth. Not withstanding are problems you are encountering, but it gets worse when you consider the times when you want to add methods in the action that aren't going to be called by buttons(ie maybe a link) or the button named "Ok" or "Save" on a page might end up calling slightly different dispatch actions (doesn't play well with lookup). It gets so ugly having to make up button labels to add into your resource file just to accomodate these situations. I find it so much more convenient to just use basic javascript and set your dispatch parameter when a button is clicked. It's clean and easy to understand and will always work. So don't give up on the basic "DispatchAction" but good choice giving up on the "LookupDispatchAction":)
-- Rick
--------------------------------------------------------------------- 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]
