>Does the stage just freeze, Director/projector freezes, or the screen
>goes blank?

The stage freezes--that is, all updating of the stage becomes impossible. 
The screen doesn't go blank, but when dialog boxes pop up, they have no 
text or controls. MIAWs will show with no content. I cannot move sprites 
onstage, can't change the appearance of a sprite in any way. UpdateStage 
has no effect.

Code continues to execute just fine. Everything is fine, except the screen 
can't be updated.

>Have you been able to make an isolated example of this bug?

I have isolated it in my code. I should be able to create a small movie 
that reproduces the problem, but I haven't done that yet. There's no doubt 
in my mind as to the cause, though.

> > getURL("event:flashAnimDone", _parent)
>
>Why do you need _parent there? Is that a param that passes the target
>path of the parent clip, or is that a param that you only need to use
>with browser windows/frames?

I'm on a kind of shaky ground, because I didn't write the Flash, and I'm no 
Flash guru. I think it's because the code is attached to a movie clip, 
though (just a first-level movie clip, not embedded in other clips). This 
isn't in a browser--it's a CD-ROM app.

>Can you post a copy of the 'flashAnimDone' handler? Maybe something in
>there is the cause?

Sure. Here it is, for what it's worth. It makes a lot of calls to other 
handlers. This is in a behavior attached to the Flash sprite.

on flashAnimDone me
   set buttonState = getButtonState(me)

   case buttonState of

     "clickedAnimE", "clickedAnimS":
       if pCurrentToggleState = #on then
         goFrame(me, "toggle") -- to show toggle #on state.
         clicked ancestor -- cause msg to be sent.

       else
         goFrame(me, "enabled") -- to show toggle #off state.
         clicked ancestor -- cause msg to be sent.
       end if


     "enablingE", "enablingS":
       if not pHasBeenEnabled then
         reportEnabled me  -- let activity know I'm ready to go.
         set pHasBeenEnabled = true
       end if

   end case
end

on getButtonState me
   set currFrame = me.pMySprite.frame
   set buttonState = getFrameLabel(me.pMySprite, currFrame)
   repeat while buttonState = EMPTY and currFrame > 1
     set currFrame = currFrame - 1
     set buttonState = getFrameLabel(me.pMySprite, currFrame)
   end repeat
   return buttonState
end

-- goToFrame handles accessing the current language art for the control.
on goFrame me, frameLabelRoot
   me.pMySprite.member.actionsEnabled = TRUE

   set langSpecificLabel = frameLabelRoot & getLanguageChar(me)
   set genericLabel = frameLabelRoot & "E"

   if findLabel(me.pMySprite, langSpecificLabel) then
     goToFrame(me.pMySprite, langSpecificLabel)
     return true

   else if findLabel(me.pMySprite, genericLabel) then
     goToFrame(me.pMySprite, genericLabel) -- default language.
     return true

   else
     return false -- couldn't go anywhere.

   end if
end

The logic gets kind of complex. The behavior sends a message (in the 
ancestor) to another object (a frame script). That causes the object to 
tell another behavior on the sprite to send its message, which in this case 
goes back to the frame script object. It does a bunch of stuff, eventually 
going to another movie.

>hard to tell what is going on, but I'd like to help.

Thanks. Actually, I've fixed the problem by converting the sprites to 
bitmaps, with film loops for the animation. Once Flash was out of the 
picture, the problem went away.

At this point, I'd just like to know if this is a legitimate bug that I 
should report. I think I'm going to be added to the beta test for the Flash 
Asset Xtra for Flash MX, and I want to make sure this next release fixes 
the half-dozen or so bugs I've found in the current (8.5) Xtra.

Cordially,

Kerry Thompson

[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to