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" <pa...@compuace.com.INVALID> 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" <pa...@compuace.com.INVALID>
    Sent: 6/25/20 5:50 PM
    To: <users@flex.apache.org>, <users@flex.apache.org>
    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." <w.p.stuur...@knollenstein.com>
    Sent: 6/25/20 5:48 PM
    To: users@flex.apache.org
    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 via email to