Well... I guess and hope I'm done ;)

I suggest anyone who used my previous build to update. (this fixes at least 1 crash and some possible crashes)
Also: it now allows one to choose whether to use system calendar/tooltip or not.
+ Mouse Button 4 and 5 can be used.
T-Clock.7z
T-Clock.zip

P.S. please check if clicking once shows calendar, and clicking again hides (of course, u'll have to enable mouse clicks first)
P.P.S. devs: can anyone with Visual Studio please check the project files? Do they still work? (I hope they do... they work with WinSDK)
https://github.com/White-Tiger/T-Clock/

edit:
New downloads here: https://github.com/White-Tiger/T-Clock/releases (always latest)

[...]
EDIT: btw thanks for releasing this build. I've been looking forward to this feature ever since the 2010 version was released.

-apex84 (August 30, 2013, 08:38 AM)

Thanks goes to 21944.450^^ He's the one who asked for it... and I was to lazy to implement it just for my little self :P
And yes, "double-clicking" might work or might not.. Still.. it's more kind of a bug (in this case the typical bug=feature thingy) I will try to do it proper next time...

currently I'm trying to implement the calendar for XP as a stand alone app which will be called from T-Clock in case you want the T-Clock calendar ;) (this reduces memory usage for those who only use the calendar from time to time and for those who use the default one)
I'm kind of a performance freak.. so it will take some time :P (as I will try to improve other stuff as well)

Anyone of the devs here against the outsourcing idea? Eg. build everything into Clock.exe or use standalone apps for "unimportant" stuff? Eg. calendar, sntp (I plan on using the sntp stuff from TClockLight kt)
The only draw back I can think of is bigger distribution size and thus a little more disk space wasted^^ And it might take a few ms longer to launch external apps such as the XP calendar, but that should be negligible (except on high PC load)