Improvements:
- It is much faster. I have shaved another 1s+ off of the rendering time, and the data is being much more consistently cached.
- I have resolved a particular problem that resulted in periodic crashes. It will now run for long periods of time and recycle correctly when the access token expires - which was the apparent problem. I have now run it successfully overnight and it will cycle up to 180 times or so then gracefully restart and carry on.
- I am working on improving the Viewers/Moderators/Bots display to make it more efficient and display in a smaller space.
- I have separated the data gathering from the display sections more effectively, which leads the way to a few other possible features in the future. The first is multicolumn displays or different layouts, the second is a user selectable font size. Currently the system does look at how many viewers you have and adjust the font size accordingly but its very difficult to test this without having each of the specific ranges of viewers present, so I think I will simply add an option in Settings to let the user adjust the font size themselves
Bugs:
I have discovered that the automatic detection of viewers who are not following is working incorrectly. I will be working on fixing that when I can determine why exactly. The detection of subscribers and VIPs seems to be working but I will be diagnosing those at the same time as I look through the function that looks for whether on not a viewer is a follower so it knows to display the symbol.
Annoyances:
I did uncover an annoying thing that in hindsight should have been very obvious but which caused me no end of frustration until I had an epiphany. A lot of data on the operation of Whozon is saved in the database, including the time for the next refresh (currently 1 min but eventually either 1 min - if you are subbed to me - or 5 mins if not subbed, once I turn the subscription system back on), as well as your color scheme selection etc. If you run the client in multiple locations - as I was doing while developing it - each of those locations will set values in the database. So my client was encountering all softs of strange anomalies and I couldn't figure out why, until I realized that the version 2.2 client I have running in OBS was setting values that were being picked up by the version 2.3 client I am working on and sometimes that caused some serious problems due to conflicts. I am going to work on a way to distinguish each client from each user in the database and make them distinct, so that this sort of conflict doesn't occur. Right now the data is stored based solely on the user's broadcaster_id from Twitch, I will see if I can add a unique fingerprint to each entry so that a user might run the client on their PC as well as on a phone or tablet without causing strange behaviour.
Status:
Version 2.3 is still currently in development and testing but if things continue to progress at the rate they are it should be live soon. The next iteration will likely be a longer development cycle as I want to focus on some internal stuff to streamline operation and improve security, and well as evolve the background maintenance cycle a bit more.