I was going to shut down the Alarm Update service today (after originally saying it would be taken offline back in April), and I realized that it hasn’t actually been working properly since I migrated my websites to Azure. So, I’ll give all the 3.5.18 and earlier users until August 18, 2016 to update, and then I’m definitely shutting it off. So, update to 3.5.19!
Today, I officially released Alarm 3.5.19. You can get it on the “Things I Work On” page, or just Check for Updates in the application. This is the first official release of Alarm since July 2011, so there is a huge amount of changes (even though it is a minor revision).
This version contains several performance enhancements and large rewrites of core areas of the application. It also updates the Update Checker to the new RWC API. It is targeted against .NET 3.5 and also removes support for Windows XP.
Please Note: All previous versions will no longer be supported as of April 10, 2016, so it’ll be a good idea for you to upgrade as soon as you can. After that date passes, the update check in the software will no longer function, and you will have to upgrade manually.
Today, I officially released Alarm 3.5.18. You can get it on the downloads page, or just Check for Updates in the application.
This version adds the ability to save and load alarm times by the File menu. It also contains a couple other minor changes. Enjoy.
I’ve been working a bit on Alarm 4 and Alarm 3.5.18, both of which are coming along nicely. I’m not quite ready for a v4.0 alpha release yet but I will be in the coming months.
It’s been really hard to work on Alarm in the past year or so as I’ve been working full time and juggling other facets of my life. I promise, however, that Alarm 4 will be released this year. I’ve been working on it in one form or another for almost three years and it’s time to give you guys a completely updated version instead of these incremental updates. So, I pledge that I will work at least 5 hours a week on Alarm and I will get it out the door as soon as possible. This means that Alarm 3.5.18 will be the last version of the v3.5 revision. I’ve said this a lot about other revisions, but I can’t keep spending development time adding features to a product that will be made obsolete soon.
Also, once Alarm 4 has been released, I will be making smaller, but complete updates more frequently. That is, v4.5 will come 1-3 months after v4.0, v5.0 will come soon after that, and so forth. The updates will not be as large as in the past, but they will be worth the update.
Finally, starting with Alarm 4.5, I will be operating exclusively on the .NET 4 platform. Also, Alarm 4 might even have two versions: one for .NET 2 and one for .NET 4, in order to make auto updating to v4.5 easier. That is just an idea, but v4.5 will require .NET 4.
As mentioned above, I am working on Alarm 3.5.18 which will be the final version of the 3.5.x versions, barring major issues. Currently, the features to be added or changed in this version are:
-Saving alarm time to a file (and associating a file extension with it)
-Option to confirm reset
-Fix for bug where tray icon flashes on startup
-Moving color scheme options into Options menu
This is a minor release, but it is the final v3.5.x version. I’m going to release it on June 9th.
I hope everyone has a great Memorial Day!
Today, I officially released Alarm 3.5.17. You can get it on the downloads page, or just Check for Updates in the application.
This version changes how easy it is to reset the alarm by accident by asking before it is reset. I have accidentally reset it in the morning and been late to work (my laptop is beside my bed), so hopefully this helps out all those out there who have had it happen.
Today I have released Alarm 3.5.16 on the site and via auto update. This version fixes a pretty serious bug that caused the Alarm to snooze/do quick alarm improperly if the 24 hour clock setting was set.
Download it on the downloads page or get it via auto update, especially if you use that setting.
Hey, I’ve had to delay v3.5.16 for a few more days as my regression tests picked up another bug. I should be able to get it fixed and re-tested by Friday.
So while working on Nighthawk, I found an issue in the snooze/quick alarm functionality in v3.5.12-3.5.15. So, I will be releasing Alarm 3.5.16 on December 4. While I’ve already finished the bug fix, I am spending a great deal of time to test and make sure something like this doesn’t happen again.
It is a pretty serious bug, but it doesn’t affect too many users. Basically, I found out that if you have 24 hour clock mode enabled and you snooze or use quick alarm between 12:00 and 23:59, the alarm time will be incorrect. If this affects you, i.e. you use Alarm in the afternoon and you use 24 hour clock, please email me at email@example.com and I will send you the fixed version immediately. Again, it doesn’t affect anyone who is not using 24 hour clock mode.
Today one of my friends found a bug when two options are enabled together, so I fixed it and pushed out 3.5.15. Get it on the site or via auto update. Alarm 4 is still on it’s way.
I just put Alarm 3.5.14 up on the site. Upgrade to it ASAP if you were using 3.5.12 (see previous post for why).