AIR Versions

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

AIR Versions

Paul Stearns
I took an application developed and running in Flex 3.6 and migrated it to AIR using Flashbuilder 4.6. It was surprisingly easy. I had a minor issue and thought I would upgrade the AIR compiler to v32.

This caused many MX components to not be found. For example;

mx:Button
mx:Canvas
mx:HBox

and the list goes on.

The choices as I see them are;

Rewriting everything to use Spark components, or

Finding an additional MX library which integrates with the current version of AIR, or

Going to an older version AIR.

I don’t think I want to rewrite using Spark, as there is a lot of code which relies on the missing mx components. Just testing would be a chore.

Is there an mx library available which will integrate with AIR 32 or higher?

What is the newest version of AIR where all of the mx components I know & love are supported? Where/how can I get it?

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588


Reply | Threaded
Open this post in threaded view
|

Re: AIR Versions

Paulus de B.
Hi Paul,

MX components should normally not be a problem. Are you sure you have the mx
namespace defined?

Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
part):

<?xml version="1.0" encoding="utf-8"?>
<s:VGroup xmlns:fx="http://ns.adobe.com/mxml/2009"
                  xmlns:s="library://ns.adobe.com/flex/spark"
                  xmlns:mx="library://ns.adobe.com/flex/mx"

Cheers

Paulus



--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: AIR Versions

Paul Stearns
Paulus:

Here is my application tag;

<mx:WindowedApplication layout="absolute"
                        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:ext="Classes.panel.*"
                        creationComplete="initApp();" xmlns:utils="Classes.Components.utils.*" pageTitle="ACETAS"
                         xmlns:vti="Classes.Input.*" modalTransparency=".2" modalTransparencyBlur="2"
                        width="1280" height="720" scriptTimeLimit="60">

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paulus de B." <[hidden email]>
Sent: 6/25/20 5:48 PM
To: [hidden email]
Subject: Re: AIR Versions
Hi Paul,

MX components should normally not be a problem. Are you sure you have the mx
namespace defined?

Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
part):

<?xml version="1.0" encoding="utf-8"?>
<s:VGroup xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"

Cheers

Paulus

--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/


Reply | Threaded
Open this post in threaded view
|

Re: AIR Versions

Paul Stearns
The actual error I am getting is;

Could not resolve <mx:HBox> to a component implementation.

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paul Stearns" <[hidden email]>
Sent: 6/25/20 5:50 PM
To: <[hidden email]>, <[hidden email]>
Subject: Re: AIR Versions
Paulus:

Here is my application tag;

<mx:WindowedApplication layout="absolute"
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:ext="Classes.panel.*"
creationComplete="initApp();" xmlns:utils="Classes.Components.utils.*" pageTitle="ACETAS"
xmlns:vti="Classes.Input.*" modalTransparency=".2" modalTransparencyBlur="2"
width="1280" height="720" scriptTimeLimit="60">

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paulus de B." <[hidden email]>
Sent: 6/25/20 5:48 PM
To: [hidden email]
Subject: Re: AIR Versions
Hi Paul,

MX components should normally not be a problem. Are you sure you have the mx
namespace defined?

Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
part):

<?xml version="1.0" encoding="utf-8"?>
<s:VGroup xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"

Cheers

Paulus

--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/


Reply | Threaded
Open this post in threaded view
|

Re: AIR Versions

Alex Harui-2
Depending on how you upgraded, you could have overwritten the default Flex configs with the default AIR configs and that could cause these symptoms.  Flex has an air-config.xml with different library-path than standard AIR SDK.

IMO, re-installing with the right AIR version has been used more than other options.  IIRC, there is a script to use to upgrade as well.

HTH,
-Alex

On 6/25/20, 2:52 PM, "Paul Stearns" <[hidden email]> wrote:

    The actual error I am getting is;

    Could not resolve <mx:HBox> to a component implementation.

    Paul R. Stearns
    Advanced Consulting Enterprises, Inc.

    15280 NW 79th Ct.
    Suite 250
    Miami Lakes, Fl 33016

    Voice: (305)623-0360 x107
    Fax: (305)623-4588

    ----------------------------------------
    From: "Paul Stearns" <[hidden email]>
    Sent: 6/25/20 5:50 PM
    To: <[hidden email]>, <[hidden email]>
    Subject: Re: AIR Versions
    Paulus:

    Here is my application tag;

    <mx:WindowedApplication layout="absolute"
    xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&amp;data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&amp;sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&amp;reserved=0"
    xmlns:s="library://ns.adobe.com/flex/spark"
    xmlns:mx="library://ns.adobe.com/flex/mx"
    xmlns:ext="Classes.panel.*"
    creationComplete="initApp();" xmlns:utils="Classes.Components.utils.*" pageTitle="ACETAS"
    xmlns:vti="Classes.Input.*" modalTransparency=".2" modalTransparencyBlur="2"
    width="1280" height="720" scriptTimeLimit="60">

    Paul R. Stearns
    Advanced Consulting Enterprises, Inc.

    15280 NW 79th Ct.
    Suite 250
    Miami Lakes, Fl 33016

    Voice: (305)623-0360 x107
    Fax: (305)623-4588

    ----------------------------------------
    From: "Paulus de B." <[hidden email]>
    Sent: 6/25/20 5:48 PM
    To: [hidden email]
    Subject: Re: AIR Versions
    Hi Paul,

    MX components should normally not be a problem. Are you sure you have the mx
    namespace defined?

    Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
    part):

    <?xml version="1.0" encoding="utf-8"?>
    <s:VGroup xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&amp;data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&amp;sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&amp;reserved=0"
    xmlns:s="library://ns.adobe.com/flex/spark"
    xmlns:mx="library://ns.adobe.com/flex/mx"

    Cheers

    Paulus

    --
    Sent from: https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691103148&amp;sdata=GuB%2FHKuLBHlLPA6KLE6YqL%2FaMS4odhvLhRl8tN%2FpSPg%3D&amp;reserved=0



Reply | Threaded
Open this post in threaded view
|

Re: AIR Versions

Paul Stearns
I am running FlashBuilder 4.6.

I created a folder C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.16.1

I copied in the 4.16 Flex SDK

I then copied the AIR compiler v32 on top of that (overwriting files as needed).

This is what I found as the proper way to do the upgrade from - https://www.andygup.net/how-to-upgrade-your-air-sdk-in-flashbuilder-4-6/



Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: Alex Harui <[hidden email]>
Sent: 6/25/20 5:58 PM
To: "[hidden email]" <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: AIR Versions
Depending on how you upgraded, you could have overwritten the default Flex configs with the default AIR configs and that could cause these symptoms. Flex has an air-config.xml with different library-path than standard AIR SDK.

IMO, re-installing with the right AIR version has been used more than other options. IIRC, there is a script to use to upgrade as well.

HTH,
-Alex

On 6/25/20, 2:52 PM, "Paul Stearns" <[hidden email]> wrote:

The actual error I am getting is;

Could not resolve <mx:HBox> to a component implementation.

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paul Stearns" <[hidden email]>
Sent: 6/25/20 5:50 PM
To: <[hidden email]>, <[hidden email]>
Subject: Re: AIR Versions
Paulus:

Here is my application tag;

<mx:WindowedApplication layout="absolute"
xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&reserved=0"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
xmlns:ext="Classes.panel.*"
creationComplete="initApp();" xmlns:utils="Classes.Components.utils.*" pageTitle="ACETAS"
xmlns:vti="Classes.Input.*" modalTransparency=".2" modalTransparencyBlur="2"
width="1280" height="720" scriptTimeLimit="60">

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paulus de B." <[hidden email]>
Sent: 6/25/20 5:48 PM
To: [hidden email]
Subject: Re: AIR Versions
Hi Paul,

MX components should normally not be a problem. Are you sure you have the mx
namespace defined?

Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
part):

<?xml version="1.0" encoding="utf-8"?>
<s:VGroup xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&reserved=0"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"

Cheers

Paulus

--
Sent from: https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691103148&sdata=GuB%2FHKuLBHlLPA6KLE6YqL%2FaMS4odhvLhRl8tN%2FpSPg%3D&reserved=0


Reply | Threaded
Open this post in threaded view
|

Re: AIR Versions

Alex Harui-2
Did you download the AIR SDK for Flex users or the main one from the “Download Now” button?
You need the one for Flex users and even then, I don’t know if this suggestion will work with recent AIR SDKs.

HTH,
-Alex

From: Paul Stearns <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, June 25, 2020 at 3:03 PM
To: Alex Harui <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: AIR Versions

I am running FlashBuilder 4.6.

I created a folder C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.16.1

I copied in the 4.16 Flex SDK

I then copied the AIR compiler v32 on top of that (overwriting files as needed).

This is what I found as the proper way to do the upgrade from - https://www.andygup.net/how-to-upgrade-your-air-sdk-in-flashbuilder-4-6/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.andygup.net%2Fhow-to-upgrade-your-air-sdk-in-flashbuilder-4-6%2F&data=02%7C01%7Caharui%40adobe.com%7C9a0f6d04716a4bd121a408d81953a800%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287194388375687&sdata=Pq%2BuBXJHKK88%2BWKSNUXCb2sooBJiO2uoMTj04w4qeGo%3D&reserved=0>




Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

________________________________
From: Alex Harui <[hidden email]>
Sent: 6/25/20 5:58 PM
To: "[hidden email]" <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: AIR Versions
Depending on how you upgraded, you could have overwritten the default Flex configs with the default AIR configs and that could cause these symptoms. Flex has an air-config.xml with different library-path than standard AIR SDK.

IMO, re-installing with the right AIR version has been used more than other options. IIRC, there is a script to use to upgrade as well.

HTH,
-Alex

On 6/25/20, 2:52 PM, "Paul Stearns" <[hidden email]> wrote:

The actual error I am getting is;

Could not resolve <mx:HBox> to a component implementation.

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paul Stearns" <[hidden email]>
Sent: 6/25/20 5:50 PM
To: <[hidden email]>, <[hidden email]>
Subject: Re: AIR Versions
Paulus:

Here is my application tag;

<mx:WindowedApplication layout="absolute"
xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&reserved=0"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
xmlns:ext="Classes.panel.*"
creationComplete="initApp();" xmlns:utils="Classes.Components.utils.*" pageTitle="ACETAS"
xmlns:vti="Classes.Input.*" modalTransparency=".2" modalTransparencyBlur="2"
width="1280" height="720" scriptTimeLimit="60">

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paulus de B." <[hidden email]>
Sent: 6/25/20 5:48 PM
To: [hidden email]
Subject: Re: AIR Versions
Hi Paul,

MX components should normally not be a problem. Are you sure you have the mx
namespace defined?

Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
part):

<?xml version="1.0" encoding="utf-8"?>
<s:VGroup xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&reserved=0"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"

Cheers

Paulus

--
Sent from: https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691103148&sdata=GuB%2FHKuLBHlLPA6KLE6YqL%2FaMS4odhvLhRl8tN%2FpSPg%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C9a0f6d04716a4bd121a408d81953a800%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287194388375687&sdata=fE%2Fm3Jp9eAgJ9aHQrYd61gn45Jh7%2BBfti5xDYTrCeV0%3D&reserved=0>



Reply | Threaded
Open this post in threaded view
|

Re: AIR Versions

Paul Stearns
I had missed the flex button, and was using the compiler button. Once I chose the right button things worked much better.

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: Alex Harui <[hidden email]>
Sent: 6/25/20 6:24 PM
To: "[hidden email]" <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: AIR Versions
Did you download the AIR SDK for Flex users or the main one from the “Download Now” button?
You need the one for Flex users and even then, I don’t know if this suggestion will work with recent AIR SDKs.

HTH,
-Alex

From: Paul Stearns <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Thursday, June 25, 2020 at 3:03 PM
To: Alex Harui <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: AIR Versions

I am running FlashBuilder 4.6.

I created a folder C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.16.1

I copied in the 4.16 Flex SDK

I then copied the AIR compiler v32 on top of that (overwriting files as needed).

This is what I found as the proper way to do the upgrade from - " target="_blank">https://www.andygup.net/how-to-upgrade-your-air-sdk-in-flashbuilder-4-6/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.andygup.net%2Fhow-to-upgrade-your-air-sdk-in-flashbuilder-4-6%2F&data=02%7C01%7Caharui%40adobe.com%7C9a0f6d04716a4bd121a408d81953a800%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287194388375687&sdata=Pq%2BuBXJHKK88%2BWKSNUXCb2sooBJiO2uoMTj04w4qeGo%3D&reserved=0>

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

________________________________
From: Alex Harui <[hidden email]>
Sent: 6/25/20 5:58 PM
To: "[hidden email]" <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: AIR Versions
Depending on how you upgraded, you could have overwritten the default Flex configs with the default AIR configs and that could cause these symptoms. Flex has an air-config.xml with different library-path than standard AIR SDK.

IMO, re-installing with the right AIR version has been used more than other options. IIRC, there is a script to use to upgrade as well.

HTH,
-Alex

On 6/25/20, 2:52 PM, "Paul Stearns" <[hidden email]> wrote:

The actual error I am getting is;

Could not resolve <mx:HBox> to a component implementation.

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paul Stearns" <[hidden email]>
Sent: 6/25/20 5:50 PM
To: <[hidden email]>, <[hidden email]>
Subject: Re: AIR Versions
Paulus:

Here is my application tag;

<mx:WindowedApplication layout="absolute"
xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&reserved=0"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
xmlns:ext="Classes.panel.*"
creationComplete="initApp();" xmlns:utils="Classes.Components.utils.*" pageTitle="ACETAS"
xmlns:vti="Classes.Input.*" modalTransparency=".2" modalTransparencyBlur="2"
width="1280" height="720" scriptTimeLimit="60">

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paulus de B." <[hidden email]>
Sent: 6/25/20 5:48 PM
To: [hidden email]
Subject: Re: AIR Versions
Hi Paul,

MX components should normally not be a problem. Are you sure you have the mx
namespace defined?

Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
part):

<?xml version="1.0" encoding="utf-8"?>
<s:VGroup xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691093154&sdata=Bf9FWbbfxZQNEmOX%2BAroUCCz5xC4bVadTwiqtwbq1UY%3D&reserved=0"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"

Cheers

Paulus

--
Sent from: " target="_blank">https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C6620518e86704f4c3a8208d819521917%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287187691103148&sdata=GuB%2FHKuLBHlLPA6KLE6YqL%2FaMS4odhvLhRl8tN%2FpSPg%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C9a0f6d04716a4bd121a408d81953a800%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637287194388375687&sdata=fE%2Fm3Jp9eAgJ9aHQrYd61gn45Jh7%2BBfti5xDYTrCeV0%3D&reserved=0>