Good catch! Yes, that should have been pValue. One should always be wary of untested e-mail Lingo!

This is an important thing for beginning behavior writers to understand. The idea is that you can set a property variable (in this case 'pValue', rather than 'theValue') in one handler, and the value stored into the property variable will be remembered across different calls within the same behavior. So, later when the mouseUp handler is called by Director, the value stored into pValue will still be there.

Thanks Nik!

At 10:48 AM +0000 1/24/03, nik crosina wrote:
 > property pValue
 property spriteNum

 on beginSprite me
    sName = sprite(spriteNum).member.name
    theValue = value(the last char of sName)
 end

 on mouseUp me
    SomeHandlerThatWillCheckForCorrectness(pValue)
 end
should that be:
pValue = value(the last char of sName)
??

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

--

Lingo / Director / Shockwave development for all occasions. (Home-made Lingo cooked up fresh every day just for you.)
[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