On 18/12/2008, at 8:25 AM, Andrew Lindesay wrote:
Ignoring the additional JavaScript stuff, I tend to do one of two
things;
1) let the data get sucked into the EO-s and then do any "last
minute fiddles" in an override of "takeValuesForRequest"
2) actually store the data into an intermediate non-EO model object
and then in the override of "takeValuesForRequest", splay that out
into EO's as appropriate.
So, I would override "takeValuesFromRequest", look to see if the
value in the pop-up was set to non-NULL by looking at the value in
the EO and then reset the string value in your EO.
OK, thanks. Might be neater than what I did, which was set a flag
based on the request values, then call super.takeValuesFromRequest()
at the end, so that the relevant child component action methods can
see the flag when they're called.
Thanks Andrew and Chuck.
--
Paul.
w http://logicsquad.net/
h http://paul.hoadley.name/
_______________________________________________
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]
