> I published for Shock10, > I have a np32dsw.dll 10.1 and a shockwavePlugin.class of > 2/10/2003 10:00PM (dont know what this class is for?)
Don't do the above when needing to verify which player version you have installed. Either make a simple test movie of your own that checks the player version using code (_system.environmentPropList) or go here in various browsers: http://www.macromedia.com/shockwave/welcome/ Remember that there is one system installed player, then there will be a plug-in and an ActiveX control that point each browser to that system installed player. The above URL tests both the Shockwave and Flash players. > Any idea? Yeah, but the honest truth is that my idea is that you're doing something wrong as it all seems to work on my end. When I provided that previous suggestion I tested in a browser to be sure before posting my response (Firefox on WinXP to be specific). I haven't seen any details about your "activate and deactivate handlers" and how those affect the code you run elsewhere. The point is this, you will continue to get the mouse events regardless of scriptExecutionStyle, but using activateWindow and deactivateWindow handlers that respond to the window being backgrounded or moved to the foreground, you can set flag variables as needed. For example: -- in a movie script global gAreWeOn on startMovie gAreWeOn = true end on activateWindow gAreWeOn = true end on deactivateWindow gAreWeOn = false end Then elsewhere: -- in a behavior global gAreWeOn on <someMouseEvent> if gAreWeOn then -- do something here to respond to the mouse event end if end The primary point of my suggestion was that in previous player releases you never received activate/deactivateWindow events in the browser, so we added those to the player event structure for v10 for just this kind of usage in the browser. Please provide some more details about what you're doing in your activate/deactivateWindow handlers and how those are affecting your mouse event handlers found in various behaviors in your movie. And because I'm the sort that likes to earn extra credit, I posted a test movie that confirms for me that things are working as I say they should (using Firefox on WinXP and Safari on OSX): http://poppy.macromedia.com/~thiggins/bugs/mouseEvents/mouseEvents.htm http://poppy.macromedia.com/~thiggins/bugs/mouseEvents/mouseEvents.dir Open the HTML page in a browser window, rollover the button and on mouseEnter I fire off an alert. Ok, good. Now activate another window but leave the first one with the SW piece visible. Now rollover the button again (without activating the window), I get no alert. Download the source as it uses the simple code above, maybe it will help highlight where your movie/technique is different from mine. Cheers, Tom Higgins - Technical Product Manager Macromedia Director and the Shockwave Player http://weblogs.macromedia.com/thiggins/ ... [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!]
