Welp that makes sense. I'm done working on this stupid thing for the night but I'll give it a try tomorrow and let you know if I'm still having problems. Thanks for your help
-Jason -----Original Message----- From: Tab Julius [mailto:[EMAIL PROTECTED]] Sent: Monday, July 29, 2002 6:11 PM To: [EMAIL PROTECTED] Cc: '[EMAIL PROTECTED]' Subject: Re: <lingo-l> Ripping my hair out (re: imaging lingo and v-12) If the mouseUp handler that you're talking about is within the MIAW, then what is happening is that you are forgetting the very movie you are running, and after the command to forget is done, it gets lost because there's no place to go. Effectively, you're pulling the rug out from under your feet. The proper way to do it is something like this (you may want to modify if you have a lot of windows closing at once): on mouseUp global gWindowToKill gWindowToKill =the activeWindow end And in the main movie, on a regular basis check for the variable; on idle --(or exitframe or whatever) global gWindowToKill if not voidP(gWindowToKill) then forget gWindowToKill gWindowToKill =VOID end if end This shifts the forget command so that it happens when you're operating in the context of the main movie, so you're not hurting anything. You will still have a place to return to. - Tab At 05:56 PM 7/29/02, Jason Whiting wrote: >I keep getting this error. It happen 1 out of 5 clicks and on >everymachine we test on. I have a main movie that open a MIAW. With in >this window an image is loaded onto the screen. This image is swaped >out on clicks. This error happens when the user clicks the close >button. The script on the close button is > >On mouseup > forget movie "display" >End > >The error happen right away after the click > >Below is the error. The registers and the stack dump change but the >rest is always the same. Anyone know what the heck is going on? I'm >using 8.5.1 on 98 but we've tested it on many configuations and it >keeps happening. Thanks for any help. > >-Jason > > >PROJECTOR caused an invalid page fault in >module IML32.DLL at 0187:6906db9c. >Registers: >EAX=04e5ac7c CS=0187 EIP=6906db9c EFLGS=00010246 >EBX=00000000 SS=018f ESP=0062edec EBP=0062f080 >ECX=04e5d2d8 DS=018f ESI=00000001 FS=a237 >EDX=00000003 ES=018f EDI=04e5d2d8 GS=0000 >Bytes at CS:EIP: >66 8b 4e 10 8b d1 81 e2 f8 ff 00 00 81 fa d0 ca >Stack dump: >04e5c928 04efa834 00000000 690067b5 04e5d2d8 68014191 04e5d2d8 04efa834 >00000000 04cb5ba8 680b4ef1 04f5b8b4 04cace16 0062eec4 0062eec4 0062eea8 >[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!] [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!] [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!]
