<?xml version="1.0" encoding="utf-8"?>
<s:Application
xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx">
<fx:Metadata>
Ev* should complete to [Event...]
Mana* should complete to [ManagedEvents]
</fx:Metadata>
</s:Application>
Currently those templates are in context "AS3". I am not sure about the best solution to fix this. Possible solutions would be:
Duplication of all relevant templates and add them to MXML and AS3 context (but duplication is not good)
Change context of fx:Metadata to AS3 (side effects?)
Allow temlates to be in 2 contexts (AS3 and MXML) (maybe im impossible, requires UI changes in the preference page)
Description
<?xml version="1.0" encoding="utf-8"?>
<s:Application
xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx">
<fx:Metadata>
Ev* should complete to [Event...]
Mana* should complete to [ManagedEvents]
</fx:Metadata>
</s:Application>
Currently those templates are in context "AS3". I am not sure about the best solution to fix this. Possible solutions would be:
Duplication of all relevant templates and add them to MXML and AS3 context (but duplication is not good)
Change context of fx:Metadata to AS3 (side effects?)
Allow temlates to be in 2 contexts (AS3 and MXML) (maybe im impossible, requires UI changes in the preference page)
This was a design decision long time ago.
At the moment in Metadata a CDATA block is necessary.
In a click-tag also CDATA block does not work currently.
Only click attributes allow AS3-Code.
Stephanie Swiderski added a comment - 16/Sep/10 06:01 PM This was a design decision long time ago.
At the moment in Metadata a CDATA block is necessary.
In a click-tag also CDATA block does not work currently.
Only click attributes allow AS3-Code.
At the moment in Metadata a CDATA block is necessary.
In a click-tag also CDATA block does not work currently.
Only click attributes allow AS3-Code.