Incidentally, could my use of an ALERT wrapper (I've been using it only
during development and only for testing purposes) be part of my problem? Ie,
is this command leaving A4D halfway through execution, not allowing A4D to
clean up some memory?
In a word, yes.
(you're probably going to tell me that the
documentation explicitly warns against doing this sort of thing...in which
case, my apologies).
No, but I will tell you that I devoted an entire chapter to describing in detail the debugging tools that go way beyond ALERT and are designed to work with Active4D.
If you want to stop execution and see a value, do this:
write(something) exit
If you want to follow values without stopping execution, use 'write to console'. To paraphrase the immortal Obiwan Kenobi, "Luke, use the manual!"
Regards,
Aparajita Victory-Heart Productions [EMAIL PROTECTED] www.aparajitaworld.com
"If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoylibrary.com
