Re: WOPopupButton and DirectAction
Re: WOPopupButton and DirectAction
- Subject: Re: WOPopupButton and DirectAction
- From: Baiss Eric Magnusson <email@hidden>
- Date: Mon, 28 Mar 2005 19:40:57 -0800
Restatement of the problem: creating a DirectAction app out of a
session based app by removing all the action bindings on the page.
I removed the <?curRegionName> binding of the WOPopupButton and added
the binding
name "regionPopupIndex";
because that's what comes thru, it's the index of the popup, not the
selection.
This works for me, in a limited sense, as I have the <list> in the
application, but I don't think it would work in most situations.
But I get the binding for <regionPopupIndex> even when the form's
action is triggered from the <Login> button.
So I need to know which widget is triggering the form's action, so when
I come from the Login button I will go to the Login page and when I
come from an <onChange> of the Region popup I will just re-generate the
calendar for that region, and there will be other widgets which will
trigger a form's actions.
I suppose I could put multiple form's on the page, does that seem like
a valid solution?
It helps to think about the HTML that you need generated. A lot of
the component action RR loop is not used in direct actions.
I think you should take off the ?curRegionName binding and add
name = "curRegionName";
Chuck
----
Baiss Eric Magnusson
<http://www.Track-Your-Finances.com>
<http://www.CascadeWebDesign.com>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden