Thanks guys for your help, the 'current script timeout' did the trick. In my defense I did look for time out in the manual- but not as one word.
Processing takes just over 30 seconds.


Cheers


Graham



On Monday, Jun 2, 2003, at 15:22 Australia/Melbourne, Brad Perkins wrote:

At 00:03 06/02/2003 -0400, you wrote:
A simpler solution might be to upping the script time in Active4D.ini.

Better not to change the script timeout globally for one thing. Use the "set current script timeout" command as I suggested earlier.

True. I meant to suggest this simply as a debugging aid. FWIW, I've never had to up the timeouts in any of my A4D code, thus my unfamiliarilty with the command. I only remembered about the timeout in the .ini file because I stumbled across it earlier today while researching something else. It's good to know the command exists.


I suspect that Graham will find that the cause of the timeouts is the 4DIC commands. ITK-based Email code might allow him to send email from within A4D.

best,

-- Brad

ps - I had the opportunity to use the new line continuation comments in some code I wrote earlier today. Thanks for implementing that.


_______________________________________________ Active4d-dev mailing list [EMAIL PROTECTED] http://aparajitaworld.com/mailman/listinfo/active4d-dev




Reply via email to