>I wrote it in this way as well: ( by way of the property inspector - do >people use this?) > >1. I go to the behavior inspector window. >2.I click the + sign to add new behavior (behavior popup) >3. I click on the + sign for event pop-up and choose the event 'mouseEnter' >4.then I go to + sign 'action popup' and choose sprite 'change cast member'.
Sorry, you lost me on steps 3 & 4. Going through the PI (or Behavior Inspector) and + is a good way to create your own behavior. After you name the script, you can click on the script icon to bring up an edit window. To use a behavior from the library palette, though the easiest way is to just drag it onto a sprite. It will automatically be added to your cast, where you can edit it, drag it onto other sprites, etc. (If the Library Palette isn't visible, Window -> Library Palette). >However, I still think I should not be using a behavior script. Do we need >to write so many actions for each sprite? (mouseEnter,mouseLeave, cursor, >puppetsound...) If you're looking to change a sprite on mouseOver, I think you may have gotten the wrong behavior. "Rollover Member Change" is really quite a simple behavior. >So, isn't it better to learn to write lingo ? Yes. However, for simple things like rollover changes, I still sometimes use the behavior library. Some of the simpler behaviors are as good as you can write yourself, so why reinvent the wheel? Cordially, Kerry Thompson [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!]
