I don't recall if I've requested this in the past, but it would simplify debugging if the errors generated during compilation / assembly were printed to allegro.log. The fact that they are only on-screen, coupled with the losing focus KB bug, is a bit of a pain. Adding this, would be very practical.
Compiler/Assembler/Lexer Errors, to allegro.log
You sir, got yourself a deal! If Saffith and Gleeok don't make this happen I sir I will as soon as they open source it.
Tamamo wrote:You sir, got yourself a deal! If Saffith and Gleeok don't make this happen I sir I will as soon as they open source it.
I suggest that you check your inbox.
Will do.
Compile errors are already logged. Are there some that are left out?
I'm confused???
I'll check if any are not logged, but apparently, I spent so bloody much time doing it the hard way. Ekh.
What events cause allegro.log to clear, and what is the optimal way to prevent clearing allegro.log?
Is there an option at execution (e.g. command line arg) to prevent clearing the log file?
I believe it get's cleared when you start up zc or zquest
Tamamo wrote:I believe it get's cleared when you start up zc or zquest
I'm curious if there is a cmd line option to suppress clearing it.
In fact, it would be handy to have all the command-line args and line parameters for DOS/Windows, Linux, and OSX, so that I can add them to the Wiki.