5 Replies Latest reply on Aug 3, 2007 12:48 PM by Newsgroup_User

    some art of debugging in shockwave

    Level 7
      Hi.

      I have big Director-project, that should be ported to shockwave.
      All places, that could be different in projector and shockwave version were
      handled by me.
      But sometimes it still comes to errors in browser and the only thing I get
      is "Please contact the author of this content...."
      Is there any way somehow to debug shockwave version? I need to know where
      the error occured.
      Now I work through putting alerts in each second line of code but this
      procedure is very slow. Can I somehow authomatically store some
      debug-reports from shockwave content (setPref is not the solution for me,
      because it is the same as alerts - slow and know very convenient)

      Any help will be appreciated
      Orest


        • 1. Re: some art of debugging in shockwave
          Level 7
          Orest,

          What I do is put a textfield on top of everything. Maybe toggle on and off
          with a keypress. Then change my "put" statements to my own function. I use a
          function called putit and pass it a paramater. This is easy to change with
          search and replace unless you use "put" to concatonate text. Then you put
          the "put" statement in there, or reroute your put data to this text field
          and put the latest line at the bottom of the text field. Then run shockwave
          and it puts all your messages in the text window. So basically I'm saying
          set things up to put messages in a text field on your shockwave temporarily
          to work like the message window.

          One thing I've found that helps get rid of weird errors in shockwave is to
          move all your scripts to the ffirst members of your main cast. It might be
          that it could be calling a script that hasn't streamed in yet.

          Timm

          "game_dev" <jorg.mann@gmx.de> wrote in message
          news:f8po2d$7oe$1@forums.macromedia.com...
          > Hi.
          >
          > I have big Director-project, that should be ported to shockwave.
          > All places, that could be different in projector and shockwave version
          > were
          > handled by me.
          > But sometimes it still comes to errors in browser and the only thing I get
          > is "Please contact the author of this content...."
          > Is there any way somehow to debug shockwave version? I need to know where
          > the error occured.
          > Now I work through putting alerts in each second line of code but this
          > procedure is very slow. Can I somehow authomatically store some
          > debug-reports from shockwave content (setPref is not the solution for me,
          > because it is the same as alerts - slow and know very convenient)
          >
          > Any help will be appreciated
          > Orest
          >
          >


          • 2. Re: some art of debugging in shockwave
            Level 7
            Create a plain text file named 'Shockwave.ini' and place the following
            text into it:
            [Lingo]
            DisplayFullLingoErrorText=1

            Save it and place it in your Shockwave support folder, something like
            C:\Windows\system32\Macromed\Shockwave 10\
            and/or
            C:\Documents and Settings\{username}\Application
            Data\Macromedia\Shockwave Player
            • 3. Re: some art of debugging in shockwave
              Level 7
              Also, on Windows, if you set _player.debugPlaybackEnabled = 1 (in a
              #prepareMovie handler, for example) you get a message window with Shockwave.
              • 4. Re: some art of debugging in shockwave
                Level 7
                I think that deserves it's own post-it! Awesome!

                I can't tell you how many times I've gone looking for that and just got the
                alerthook stuff.

                So thanks!

                Timm


                > Also, on Windows, if you set _player.debugPlaybackEnabled = 1 (in a
                > #prepareMovie handler, for example) you get a message window with
                > Shockwave.


                • 5. Re: some art of debugging in shockwave
                  Level 7
                  Wow, thanks for that juicy bit of info from me too! :)

                  Richard Smith
                  www.funpods.com

                  "Sean Wilson" <webforumsuser@macromedia.com> wrote in message
                  news:f8rbgr$8gd$1@forums.macromedia.com...
                  > Also, on Windows, if you set _player.debugPlaybackEnabled = 1 (in a
                  > #prepareMovie handler, for example) you get a message window with
                  > Shockwave.