Yes, that is what I was refering to.  Hence, justification for the
name change.  Thanks Matt.

--- In flexcoders@yahoogroups.com, "Matt Chotin" <[EMAIL PROTECTED]> wrote:
>
> Event.result remains the same, only myservice.myOp.result changed
to
> lastResult.
>
> The reason we did it is because there was some fear over confusion
with
> the result property and the result event.  It's a semi-arbitrary
rule
> that allows the MXML compiler to figure out what you mean (in this
case
> result is a read-only property so since you can't assign to it use
the
> event).  Also lastResult makes it pretty clear that this is the
last
> result returned for the service regardless of how many times you
might
> have executed it.
>
> Matt
>
> -----Original Message-----
> From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On
> Behalf Of Tim Hoff
> Sent: Saturday, May 20, 2006 5:30 PM
> To: flexcoders@yahoogroups.com
> Subject: [flexcoders] Flex2B3 - result to lastResult
>
> I haven't changes result to lastResult yet, per the changes from
B2 to
> B3.  However, my applications still work fine.  Will result be
> depreciated in the final release?  And, why the name change? :)
>
> Curiousness,
> Tim
>
>
>
>
>
>
>
>
> --
> Flexcoders Mailing List
> FAQ:
http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> Search Archives:
> http://www.mail-archive.com/flexcoders%40yahoogroups.com
> Yahoo! Groups Links
>






--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to