Flex Custom xmlns Code Completion

I am haveing some wierd issues with Flex 4 Code compeltion on Custom components, am i doing something wrong?

I start with a basic MXML AIR Application

"Application.mxml"
<?xml version="1.0"?>
<s:WindowedApplication 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:Script> <![CDATA[ ]]></fx:Script>

    <fx:Declarations></fx:Declarations>

</s:WindowedApplication>


I create a MXML Component in com.mydomain.components

"TestComp.mxml"
<?xml version="1.0"?>
<s:SkinnableComponent 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:Script><![CDATA[            ]]></fx:Script>
    <fx:Declarations>
    </fx:Declarations>
</s:SkinnableComponent>


Back into my Application I type "<TestCom..." and I Get Code Completion of "<s:TestComp" When I complete to that it instantly turns red as TestComp is not part of the Spark namespace.


I manually add the xmlns to the application like this

"Application.mxml"
<?xml version="1.0"?>
<s:WindowedApplication  xmlns:fx="http://ns.adobe.com/mxml/2009"  xmlns:s="library://ns.adobe.com/flex/spark"
                        xmlns:mx="library://ns.adobe.com/flex/mx" xmlns:l="com.mydomain.components.*">
    <fx:Script>  <![CDATA[

        ]]></fx:Script>

    <fx:Declarations>

    </fx:Declarations>

</s:WindowedApplication>


If I type "TestComp" Code completion still gives me "<s:TestComp" but if i type "<l:" it return's "no suggestions" from the code completion,
If I type out "<l:TestComp " I now get code completion on the properties of my TestComp.mxml class.

So it seems to be able to find it, it is just not using it for code completion. It also doesn't seem to be setup to automatically add new namespaces. Is
this just the way it works? Should I not get code completion on custom MXML components until I type out the full name myself and add the namespace?

** UPDATE: This problem only seems to happen with Flex 4 SDK's. It operates as expected using the 3.5 SDK... arg....

thanks
-ross

Message was edited by: Ross Gerbasi

Please sign in to leave a comment.