Clean up ConLog, so it uses message passing to the main thread

[bagedevimo]

Will give us cleaner code, and should drop the thread count by one. I'll try and do this some time in the next week or so.

This might be the cause of quite a few "random" segfaults on *nix.

[Bigpet]

Yeah, I kind of tried a few things (reading the buffer till it's empty in one event, only passing references to already converted wxStrings, etc.) and none gave me good performance under Windows.

The issue is that if we insist on writing every single log entry to the gui and then auto-sizing the columns with each addition it's never going to be as performant as we want.

The only thing that I could imagine actually helping is to decouple the gui data from the gui drawing. So we manage the log messages that are in the gui buffer as a data collection (i.e. vector or whatever the class was) and only refresh the gui at max rate of 60 or 30 fps. This means only showing the last few entries that fit into the the log window and then loading more from the data-buffer when the user is scrolling.

[NeilAvent]

Would adding an option "log only to file" solve this? You could set that when wanting to have max performance and could use the log file rather than the GUI.

[Bigpet]

@Blaypeg that's already what happens when you tell it not to log anything

[Bigpet]

I'm guessing this is solved by #371