It's actually more of an effect on WOSubmitButton than it is on
WOForm ... WOForm calls wocontext._setIsMultipleSubmitForm(true),
then passes down to its children. For a WOSubmitButton, if the
context is multiple submit, the action on the submit button will only
be called if the submit button's name is in the form values (and it
will call wocontext._setActionInvoked(true)). In the non-multiple-
submit case, a WOSubmitButton inside the form will ALWAYS call its
action (and set wocontext._setActionInvoked(true)). When
invokeAction returns to the WOForm, the form's action binding is
called only if !wocontext._wasActionInvoked().
ms
On Feb 9, 2007, at 5:52 PM, Andrew Lindesay wrote:
Hello;
Aside from the obvious end-effect of setting "multipleSubmit" to
true on WOForm, does anybody have any insight into the behind-the-
scenes workings of WOForm and how its behaviour is altered by
setting this binding to true?
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mschrag%
40mdimension.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
