|
I was trying to demo view states today at work and made the most ridiculously simple example. I have a Widget mxml component that extends Canvas. All it does is define two states, "default" and "selected" and specifies to change the backgroundColor style from grey to pink when selected. If i create this component in a package called "temp" I get strange errors: 1202: Access of undefined property name in package temp. 1202: Access of undefined property overrides in package temp. 1202: Access of undefined property name in package temp. 1202: Access of undefined property value in package temp. 1202: Access of undefined property name in package temp. 1202: Access of undefined property overrides in package temp. 1202: Access of undefined property name in package temp. 1202: Access of undefined property value in package temp. If i copy the exact same file into another package, foo, it works fine. If i change the temp package name to bar it works fine. It leads me to believe something strange is going on behind the scenes. Any ideas? Anybody encountered other reserved name space things like this? I've updload the the source here (http://f6.grp.yahoofs.com/v1/AHa9RMsq-qNqQljPryLF4mHTt40I4W--orG60fPTck5Rq4yIvP08MzCcfTUF6rWVFmq53xX3rlHdRFdKgia_vPHvGE3_/SacredTempSource.zip). I have an instance of foo/Widget and an instance of temp/Widget inside of a Canvas. if you import this into a new Flex Project you'll see that it complains if you don't comment out the temp/Widget instance. It seems to only relate to using tags related to States. Thought this was worth noting. Thanks, Andy
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- [flexcomponents] "temp" package bug Andy McIntosh
- Re: [flexcomponents] "temp" package bug Manish Jethani
- Re: [flexcomponents] "temp" package bug Michael Schmalle
