For those of you who have been using Flex since 1.5, do you remember how Flex
always had a problem returning single-element arrays as a non-array object, and
how we had to apply mx.utils.ArrayUtils to force it to become a one-element
array?
It seems like Flex 3.0 still has the same problem. If
: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of elevight
Sent: Tuesday, April 21, 2009 9:00 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Perennial problem with Flex -- single element vs
multi-element
For those of you who have been using Flex since 1.5
] *On
Behalf Of *elevight
*Sent:* Tuesday, April 21, 2009 9:00 PM
*To:* flexcoders@yahoogroups.com
*Subject:* [flexcoders] Perennial problem with Flex -- single element vs
multi-element
For those of you who have been using Flex since 1.5, do you remember how
Flex always had a problem
3 matches
Mail list logo