7 Replies Latest reply on Jan 11, 2009 7:02 AM by Newsgroup_User

    strange bugs

    Level 7
      Hello,
      I'm using Director MX 2004(10.1) and I'm having the following problem:

      sometimes I have sript errors that "disapear"
      when I recompile the behavior or the movie script where they occur. The
      bugs don't seam "logical"
      and, for example, when I get one script error alert for an undefined
      handler, the name of the handler is strange and can vary: normaly is a
      cardinal(#) followed by a strange caracter which varies. More recently I got
      those "ilogical" bugs but the aim was a list which, in debug mode, also have
      a strange name("M" for example). To publish is worse: in editing mode I
      recompiled to "see" it working but the projector don't have the same luck,
      until "by chance" it works.
      Best regards,


        • 1. Re: strange bugs
          fazstp Level 2
          What are you doing when you get the error? Is it always at the same point in the movie?
          • 2. Re: strange bugs
            Level 7
            Hi,
            It can happen in a lot of places. When the problem seems solved and I work
            with some code the bugs appear in other places and keep themselfs in those
            places, thoug it can work fine in the most part of the aplication.
            I don't know how to explain better. It seems that the sript becomes
            corrupted when i make some changes.

            Thanks

            "fazstp" <webforumsuser@macromedia.com> wrote in message
            news:gk314n$nh8$1@forums.macromedia.com...
            > What are you doing when you get the error? Is it always at the same point
            > in the movie?


            • 3. Re: strange bugs
              Level 7

              "Daniel" <multimedia@ccbs.pt> wrote in message
              news:gk20f3$boj$1@forums.macromedia.com...
              > Hello,
              > I'm using Director MX 2004(10.1) and I'm having the following
              > problem:
              >
              > sometimes I have sript errors that "disapear"
              > when I recompile the behavior or the movie script where they occur.
              > The bugs don't seam "logical"
              > and, for example, when I get one script error alert for an undefined
              > handler, the name of the handler is strange and can vary: normaly is
              > a cardinal(#) followed by a strange caracter which varies. More
              > recently I got those "ilogical" bugs but the aim was a list which,
              > in debug mode, also have a strange name("M" for example). To publish
              > is worse: in editing mode I recompiled to "see" it working but the
              > projector don't have the same luck, until "by chance" it works.
              > Best regards,
              >

              Hi,
              what platform are you on?
              Did you convert the files from a previous version of Director?
              Are there any other problems with cast members?

              I vaguely remember some post about this, but can not find it for you
              now, sorry.

              Somehow your script members or just one of them are getting corrupted.

              Things to try (if possible):
              Do "Save and compact" instead of save
              Copy / paste the script into a new script members, and delete the old
              ones.
              Create a new movie and copy everything over to the new movie.
              Check your disks for errors (was a problem on Mac if I remember well?)

              Oh, AND:
              make backups often!
              Preferably on external disks.

              I will let you know if I find more.

              Richard



              • 4. Re: strange bugs
                Level 7
                Hi Richard,
                I'm working on Win XP, the files were made from the beggining in Director
                10.1 and i didn't find problems with other cast members.

                Thanks for your help,

                Daniel


                "LOOPING_Richard" <root@localhost.not> wrote in message
                news:gk5q04$iq8$1@forums.macromedia.com...
                >
                > "Daniel" <multimedia@ccbs.pt> wrote in message
                > news:gk20f3$boj$1@forums.macromedia.com...
                >> Hello,
                >> I'm using Director MX 2004(10.1) and I'm having the following problem:
                >>
                >> sometimes I have sript errors that "disapear"
                >> when I recompile the behavior or the movie script where they occur. The
                >> bugs don't seam "logical"
                >> and, for example, when I get one script error alert for an undefined
                >> handler, the name of the handler is strange and can vary: normaly is a
                >> cardinal(#) followed by a strange caracter which varies. More recently I
                >> got those "ilogical" bugs but the aim was a list which, in debug mode,
                >> also have a strange name("M" for example). To publish is worse: in
                >> editing mode I recompiled to "see" it working but the projector don't
                >> have the same luck, until "by chance" it works.
                >> Best regards,
                >>
                >
                > Hi,
                > what platform are you on?
                > Did you convert the files from a previous version of Director?
                > Are there any other problems with cast members?
                >
                > I vaguely remember some post about this, but can not find it for you now,
                > sorry.
                >
                > Somehow your script members or just one of them are getting corrupted.
                >
                > Things to try (if possible):
                > Do "Save and compact" instead of save
                > Copy / paste the script into a new script members, and delete the old
                > ones.
                > Create a new movie and copy everything over to the new movie.
                > Check your disks for errors (was a problem on Mac if I remember well?)
                >
                > Oh, AND:
                > make backups often!
                > Preferably on external disks.
                >
                > I will let you know if I find more.
                >
                > Richard
                >
                >
                >


                • 5. Re: strange bugs
                  Level 7
                  One thing to look out for that causes things like this is sometimes a sprite
                  may have a cast member attached to it which is NOT a behavior, but apears in
                  the Behavior Inspector as if it were. I'm not really sure what causes this,
                  but it results in symptoms similar to yours. Deleting the offending
                  non-behavior from the Inspector usually solves the problem. (Though you may
                  then have to replace it with the proper behavior.) I think this may happen
                  when you move a lot of cast members around, or create a new cast member with
                  the same name as a script cast member, I don't know. I've had it happen
                  numerous times, but I can't reproduce what actions caused it to occur.


                  • 6. Re: strange bugs
                    Wolfgang Herold Level 2
                    i use external casts with functions i need also for other projects and then deliver as cxt. sometime i forget to delete the cxt files in my project folder and that are together there with the cst file. So when i publish the new exe will use the old cxt's instead of the maybe newer cst's and i'll have also some strange errors, as projectors prefer cxt's


                    Wolfgang
                    • 7. Re: strange bugs
                      Level 7
                      Hi Daniel,

                      It is hard to tell what's the problem without having specific details of what
                      is happening. If the error comes back, I'd suggest you make a copy of that
                      problematic file, work out the steps to reproduce the problem, and then post
                      them here. If it is something corrupted or a bug in Director, I can certainly
                      help forward it to Adobe.

                      regards
                      Dean

                      Director Lecturer / Consultant / Director Enthusiast
                      http://www.deansdirectortutorials.com/
                      http://www.multimediacreative.com.au
                      email: d.utian@unsw.edu.au