At 11:49 -0400 07/30/2002, Kendall Anderson wrote:
>> >Then in the closeMiaw handler which is on your stage, have the code
>> >to close and forget your Miaw.
>>
>> No no no. Sending the call like that will result in serious and
>> painful death on some but not all Windows systems.
>
>I thought this was an issue regardless of OS, no? (given that it's a flawed
>programming technique as you mention later in your message, not an
>OS-specific item)...
It's flawed in the sense that it's a little on the crufty side, but
ostensibly Director/Lingo is tough enough to handle that (that's why,
for instance, we don't have var typing). I don't personally like the
logic of self-disposing objects anyway, but that's my problem. ;)
But it's a significant *system* problem on Win, which has a way of
folding up weeping if you do any disposing of MIAWs without properly
purging their resources first. Mac is *considerably* more forgiving
in this regard.
You can write stacks of bad (or at least questionable) MIAW calls in
Mac and get away with it, and watch things sort of explode on Win
when they execute there. In a way it's almost beautiful, provided
you've got a serene nonattachment to results.
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://shop.osborne.com/cgi-bin/osborne/0072195622.html
[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!]
