3 Replies Latest reply on Jun 21, 2011 8:51 AM by tkong66

    Flash Catalyst CS5.5, Incompatible Component

    bvacc

      Hello all,

       

      I've noticed in CS5.5 that many of the custom components I create become uneditable upon saving, closing, and reopening my project. The floating properties panel indicates that the component is compatible with FC, and that I need to use Flash Builder to edit its contents.

       

      I'm not sure exactly what causes this to occur yet, but it has happened with custom components that have multiple states, and custom and library components that control transitions between those states.

       

      As far as I can tell, I am not doing anything differently in my workflow than I have in CS5 or Panini.

       

       

      So my question is, can I work around this message and edit my components in FC? And barring that, what exactly is causing this to happen only after I close and reload my file?

       

      Thanks!

        • 1. Re: Flash Catalyst CS5.5, Incompatible Component
          levancho Level 3

          +1 I would like to know more about that message as well

          • 2. Re: Flash Catalyst CS5.5, Incompatible Component
            tkong66

            I am having the same problem.

             

            I have attempted to get into Flash Builder to see what the matter was.  Encountered a problem there as well.

             

            "Description Resource Path Location Type

            The property spark.components.Group.height must be a number in the range [0, 4000]. grPhotoGalleryCustomComponent1.mxml /Raintree Hotel - June 2011 v018/src/components line 7 Flash Catalyst File Incompatibility "

             

            Am guessing from above that my component is over the 4000 px limit.
            vivala adobe
            • 3. Re: Flash Catalyst CS5.5, Incompatible Component
              tkong66 Level 1

              Hmmm... I have decided to give it a go mucking again in Flash Builder to see whats going on.

               

              And I'm pretty sure I have found a workaround, as follows:-

               

              1. In FB, goto PROJECT>FLASH CATALYST>IMPORT FLASH CATALYST PROJECT..

              2. BROWSE to choose your "faulty" .FXP   , click FINISH

              3. In PACKAGE EXPLORER, trail down to [FXP_NAME]>SRC>COMPONENTS..

              4. You will see your .MXML corresponding to your "faulty component"

              5. Double-click the component and a similar script to below will show.

               

              For the HEIGHT value i have changed mine from "6422" to "2246" :-

               

                <?xml version="1.0" encoding="utf-8"?>

                <s:Group xmlns:s="library://ns.adobe.com/flex/spark"

                xmlns:fx="http://ns.adobe.com/mxml/2009"

                     xmlns:graphics="assets.graphics.*"

                  xmlns:d="http://ns.adobe.com/fxg/2008/dt"

                  xmlns:fc="http://ns.adobe.com/flashcatalyst/2009"

                  width="494" height="6422">

               

              6. SAVE the file

              7. RIGHT-CLICK on the [FXP_NAME], choose FLASH CATALYST>EDIT PROJECT IN FLASH CATALYST..

               

              That's it!

              I'm guessing any number <4000 should work. I have saved the file again in FC and rebooted, and reopened the fxp without seeing the error again.

              Lemme know if this works on your side.