On 25/09/2013 20:55, aYo ~ wrote:
In developing mxml classes using code behind I've often accessed protected
class variables via the mxml attributes. I believe it's allowed
Yeah, me too - the MXML is extending the base class, so of course gets
access to package-local variables.
Tom
In developing mxml classes using code behind I've often accessed protected
class variables via the mxml attributes. I believe it's allowed
aYo
www.ayobinitie.com
mrbinitie.blogspot.com
On 25 Sep 2013 20:11, "Alex Harui" wrote:
> @Gordon (mostly):
>
> I ran into a situation where someone is setti
MXML protected vars as attributes
@Gordon (mostly):
I ran into a situation where someone is setting protected variables via MXML
attributes. Is this "allowed"? I thought MXML attributes were only for public
properties. MXMLC lets this happen. Falcon does in one case, but not
@Gordon (mostly):
I ran into a situation where someone is setting protected variables via
MXML attributes. Is this "allowed"? I thought MXML attributes were only
for public properties. MXMLC lets this happen. Falcon does in one case,
but not another. What should Falcon do?
MXMLC and Falcon a
