3 Replies Latest reply on May 18, 2011 7:49 PM by Lampei

    Designer warnings in MXML codeview - preventing work - DesignAssetLoader.completetimeout

    YNAB Level 1

      I am in the process of upgrading my project to Flex 4.1 from Flex 3.5. As part of this effort, I have downloaded the Burrito build. There is currently an error that is preventing me from working:

      When I open an MXML file in code view (not attempting to use the designer), my "problems" window begins to fill up with warnings like the following:

       

       

      Design mode could not load AlivePDF.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)

      Design mode could not load AlivePDF.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)

      Design mode could not load AutoComplete.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)

      Design mode could not load AutoComplete.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)

      Design mode could not load FlexSpy.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)

      Design mode could not load FlexSpy.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)

       

      I would be content to ignore these errors, however the warnings pane steals focus every time a new warning gets added! That means I cannot type in my MXML file until the warnings are finished, which usually takes about 30 seconds for _each_ MXML file. I have attempted to disable the Designer in every way I know how through the preferences. Here is a picture of my Design Mode preferences:

       

      The only thing checked is "Always open MXML files in code editor". I hoped that having "automatically show design-related views" unchecked would prevent the designer from trying to do anything in the background, but alas...

      I literally never use the designer, so I would be happy to disable it completely if it could get rid of these errors. Anything you could offer would be greatly appreciated!