On the surface it looks like I've done sweet FA but what you can't see here is a great deal behind the scenes:
1) Settings class is slowly being converted to use INotifyPropertyChanged, and will evenetually be event driven to work with the UI completely. I'm just finishing all that up now.
2) The console output, though it looks no different, is now using a bound DataGrid. This is far less hacky then using a grid and updating with the code behind. Now, to update the UI with a new message, I just do: Messages.Add(...); A massive differernce.
3) I've managed to link up some of the settings already to the settings class. They don't do much but as a proof of concept it all works in both directions now. I can change a setting from the UI, and update the UI from a setting.
These 3 changes are a very big deal for the program now. I spoke with Kujo the other day and what needs to happen from here is:
1) Finish redesigning the settings.
2) Finish adding bits and pieces to the User Interface and link that to the settings.
3) Finish up the remaining packets.
4) Start with beta releases and testing, adding new features as I go.
Also: WPF is hard.
EDIT: Settings complete, but for converting some fields to properties. Quite organised and easy to use now. Logical.
I need tore-work how data comes into the console. I'm converting to objects as the messages come in, where I should instead reference the raw message, and use a converted to put it into textblock format. That should hopefully not take long but I'm ready to be made a fool of.
I'll be quite happy when I have the settings driving the UI fully and vice versa...