Hi John Having just read through your code below as well as John Trentini's reply to this email, I'm a little confused as to what exactly your doing or attempting to do. However I'm going to make a few assumptions and then try to explain a solution from there.
1). I'm assuming this behaviour is attached to the sprites that you are attempting to get values for member name and loc for. 2). sprite(150) is infact the field sprite that is following the mouseLoc around on the stage. Because there is no offset value, the field will always appear to begin drawing to the right and below the tip of the arrow cursor. - so the larger question that you have, is whether or not mouseEnter, mouseWithin, mouseLeave and mouseDown events work for sprites that are offstage.. vs whether or not the mouseLoc gets updated while your offstage. And if I read your code correctly, the biggest culprit is whether or not mouseWithin would continue updating when offstage as that is what is feeding your field information on mouseLoc and moving your field around the stage. I've never seen them not work while not offstage and have just made a sample movie based on your code and my tooltip continues to work offstage (at least in authoring). However, John Trentini pointed out a major potential flaw / misunderstanding in your code, that is that you are reporting only the loc of the sprite you are hovering over, you aren't reporting the mouseloc in the output field. Therefore it is entirely understandable that your reporting field would continue to display the current items loc even if you move the mouse offstage provided of course the sprite is also covering the area that your mouse is over in the offstage area. Now there is one thing that is exceptionally confusing to me, and that is your description of the fact that the field does not leave the stage area and does not update while the mouse is offstage. Unless you have constrained sprite(150) to stay onstage as John Trentini has hypothesized. There is one other potential explaination that better describes what you are seeing. If your stage is the size of your monitor, or you are positioning the left side of the stage against the left most edge of your monitor. You will notice, that the mouse stays at the left most edge of the monitor and does not continue to move into no mans land when you leave the monitor (or the left most monitor in multimonitor displays). At least that is the case under Win2K, the tip of the arrow is just off screen). If you take a sprite and move it entirely or partially offstage to the left as described above, then you can get a situation where the mouse does not update when it is against the left bound of your display giving the exact behaviour that you described in your earlier emails. Not sure if any of this helps you Sincerely Mark R. Jonkman [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!]
