Flex code completion of static const in mxml causes odd behavior?

I've seen an odd behavior when I try to use code completion on a static const defined in that file. The code completion gives me the fully qualified name of that class and somehow triggers a format of everything within the <mx:Script> tag.

Since I've figured out the cause I'm able to avoid this for now and just not use code completion for static const's.

I'm running v9.0.1, build 93.94 under JDK 1.6.0_17 on OS X Leopard.

3 comments
Comment actions Permalink

This appears fixed in the latest EAP.

0
Comment actions Permalink

Hello Nathan,

Yes, this could be an http://youtrack.jetbrains.net/issue/IDEA-26755.

Regards,
Kirill

0
Comment actions Permalink

Yes, seeing that in the EAP changelog was what prompted me to install EAP.

0

Please sign in to leave a comment.