I've said it in the past; developers must stay humble. Humility just hit me again.
Have you heard the news? slimKEYS 1.1.0 is out! You're already using slimKEYS? So you may already know it uses an auto-updater to periodically check for updates. If you knew that, you're probably waiting for the updater to find the update, right?
Wait no more... It won't happen... (blush)...
You see, I'm using Advanced Installer's auto-updater application. When building my package, it creates a small executable named "slimCODE.slimKEYS.AutoUpdate.exe" with a sibling INI file with settings. My application has to call this executable from time to time to perform all the auto-updating stuff... (cough)...
Where did I put the code to call this executable? In the timer callback that closes the splash screen. What happened with the splash screen since version 1.0.4? It's gone!
Argh!
By killing the splash screen, I've killed auto-updates. Quite a bad implementation, my friends. Not only does this mean many of you won't see version 1.1.0 until you discover it's out, but you were running 1.0.4 instead of 1.0.5 for quite some time now.
What amuses me the most about the situation (hey, gotta laugh about this) is that auto-updating from 1.0.3 to 1.0.4 killed the feature. Ironic.
What amuses me less is that I saw the signs, but did not catch them. My logs for the file that is checked by this auto-updater were strange. Only a couple of accesses per day. I should have figured out there was a problem. And no, auto-updating wasn't part of my pre-release tests. Now it will be.
I've now fixed this issue and updated the package to version 1.1.1.