UserError, which is an exception that should be caught and shown to a live user client in the main window. ie, they tried to touch an object that didn't exist or something
ClientError, which is a lower-level exception that the tm client itself needs to handle. it may or not be shown to a live user.
We need another type of error stream; something like ScriptedObjectError.
This is more complex than the other two since they're errors that a human should see but might not be logged in to see.
My current sketch for this:
[ ] new ScriptedObjectError model
relates to a scripted object's author
knows when it was created
[ ] WITCH runtime errors create a save an error row
[ ] error console in WITCH pane shows the last n ScritedObjectErrors for the logged in user when the look at it
[ ] audit all errors and handle differently if they are coming from an automated actor
Right now we have two exception classes:
UserError, which is an exception that should be caught and shown to a live user client in the main window. ie, they tried to touch an object that didn't exist or somethingClientError, which is a lower-level exception that the tm client itself needs to handle. it may or not be shown to a live user.We need another type of error stream; something like ScriptedObjectError.
This is more complex than the other two since they're errors that a human should see but might not be logged in to see.
My current sketch for this:
authornScritedObjectErrors for the logged in user when the look at it