when/why is pupperSprite necessary?

[Slava Paperno]

I thought the puppetSprite command became more or less unnecessary a few 
versions ago, and that a sprite's behavior can now be controlled through 
Lingo in almost all situations, but I'm finding that I can't live without 
this command any more in Dir MX (Windows XP).

This used to work without puppetting

sprite(1).member = member("MyText", "Texts")
--you see the text of the member on the stage
sprite(1).member = member("MyBitmap", "Bitmaps")
updateStage
--you see the bitmap on the stage
But this simple sequence no longer works for me (in projector or in 
authoring). After the second command, I still see the text on the stage, 
even though the Message window tells me the sprite's member is a bitmap:

put sprite(1).member.name
--"MyBitmap" --BUT I see the text--the stage hasn't been updated.
This solves the problem:

sprite(1).member = member("MyText", "Texts")
puppetSprite 1, true
sprite(1).member = member("MyBitmap", "Bitmaps")
puppetSprite 1, false
updateStage
--I see the bitmap on the stage
I see the same story with setting sprite(1).visible to false and then true: 
the Message window tells me the prite is visible, but it's not on the stage 
unless I puppet it.

What's the story?

Slava

[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!]