Originally Posted by
XtrmJash
I'm using TortoiseSVN locally, and the google standard SVN server, so it does support storing deleted code, but using a Removed Code.txt just makes it easier to recycle old code if I need to... I prefer it, and it's only a couple of KB I think.
As for the error logging, basically there will be an output window which will log each function that is called within the bot. That means say you call getClients() and one or more clients returns a null value, or throws an exception, the end user can see this error, and I will eventually add a crash handler to dump the log to a text document which they can use to report the issue. On top of that, the Lua functionality will have an output window, which will track all thrown lua exceptions, and once again dump them to a text file... I know from experience that engines are notoriously difficult to trace, hence the desire to add a logging function to both the Lua engine and the bots own code... That way if the Lua engine encounters an error I can tell if it's a bug in my code or in a script almost instantly.
The logging is functional at the minute, so if you want you could download and compile and check the test program. Under "General" there is a logging settings pane, consisting of "Error level", which sets the type of errors to log (e.g Warnings - it will log all warnings and more serious error messages, or just Information, which logs every single message and function call). The logging at the minute has actually proven quite useful in resolving my getClients function, as well as some GUI update issues which were caused by multiple threads trying to update the same GUI element... It's already proving to be worth far more than the time I invested setting it up :P