On Thursday, February 27, 2003, at 02:19 PM, Richard Gaskin wrote:
Can you pin down the script that's running when the error is thrown?Thanks for the info
It sounds like it's something I can't do much about. It's been reported by a
user so I'll try and get more info about where it's happening in the app. It
sounded to me like it is hapenning alot???
Not in the MC engine, and since we're talking about a standalone (we are,
aren't we?), then it seems unlikely that the Rev IDE could be a contributing
factor.
Determining a recipe for this might be very useful in helping the Rev 2.0
engine make sure this doesn't happen, and may provide us with a way to
implement a workaround in the meantime to keep your work running smoothly.
Though they may seem chaotic, computers are ultimately deterministic
systems, meaning simply that the same actions will produce the same result.
Once we can determine the difference between actions that trigger the crash
and those that don't, the issue will likely become resolvable.
Sometimes it takes a bit of sleuthing, but I've never seen an error that
ultimately couldn't be resolved one way or another, whether in script or the
engine or both.
If your user Monte will do this, have them run macbugs and see if they can get the error. They can then save out the log file. Send it to Scott for review. He always figures this out once he has that file.
Best regards, Mark Talluto http://www.canelasoftware.com
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
