>To answer your question about void: #void is not void, it is a symbol. >Try >this: > >put void >-- <Void> >put ilk(void) >-- #void >
So I should be using void. 1. When I tried to put empty in the message window, I received this message " ". Is that what you meant when you wrote later on in the message: >The reason for this is that do "" will simply take up time, but >nothing >will happen. Is this equivalent to empty? > Since this will automatically be the "Original member" of the >sprite, you kill two birds with one stone: > >on getPropertyDescriptionList(me) > tPropertyList = [:] > > if the currentSpriteNum then > tDefaultMember = sprite(the currentSpriteNum).member > else > tDefaultMember = member 1 > end if > > tPropertyList[ \ >#OriginalMember] = [ \ >#comment: "Original member:", \ >#format: #bitmap, \ >#default: tDefaultMember \ >] > 2. Why does this work for OriginalMember only? When I used it for RolloverMember as follows, tPropertyList[ \ #RolloverMember] = [ \ #comment: " Rollover member:",\ #format: #bitmap, \ #default: tDefaultMember\ ] I receive an error message: Variable used before assigned a value. How could this be? >Note that I test whether the currentSpriteNum is not void, and I >provide a >different default value if it is. This is because Director >also calls the >getPropertyDescriptionList() handler when it recompiles >the behavior >script. >It does this to check if the property list has changed, so that it can > >warn you that the properties and values you previously used may now be > >invalid. >When it does this, the currentSpriteNum is void, because Director is >concerned simply with the script and not with any sprites the behavior >script may be attached to. > 3. Does this not mean that the getPropertyDescriptionList get executed twice since it is recompiling the behavior, as it is already complied at author-time? tPropertyList [ \ #pActionSound] = [ \ #[comment: " Action Sound ", \ #format: #sound , \ #default: "mouse click" 4. Is pActionSound equivalent to: on mouseDown me puppetSound 3, member "mouseclick" >change this to: > >if pActionLingo <> "" then > do pActionLingo >end if > >The reason for this is that do "" will simply take up time, but >nothing >will happen. 5. So why was it used? For sound how many properties need to be specified? It is stated in the Director Help that the behavior�s Parameters dialog box opens in three circumstances: a. after the user drags a behavior to a sprite or frame b. when the user double-clicks the behavior in the Behavior Inspector dialog box c. when the user clicks the Parameters button in the Behavior Inspector 6. Sorry, how is a. done? I don�t drag a behavior to a sprite. Isn�t this the way to create a behavior ? I drag a cast member to the stage or score, this becomes a sprite. I right click on the sprite, then start typing in the script box which opens. b. when I double click on the behavior in the dialog box, nothing happens. There is a line in the box � 10 (internal) behavior(not compiled). I clicked the play button, then the words not compiled disappeared. But still the box still didn�t appear. c.when I click on the parameters button in the behavior inspector, there is nothing. Rather, the two wheels are faded out. Why is that? How do I open the Parameters dialog box? Thanks very much for your help. It is appreciated. Genevieve _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/LUJ/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!]
