if you're using portable mode / T-Clock.ini, please create a backup before updating!!!

This version fixes most stuff broken by the Windows 10 anniversary update (exception: default tooltip)
It's probably not as stable as previous releases so watch carefully and report any bugs you may encounter.

changes

• ! clock working once again on Windows 10 with anniversary update applied (#39, #41)
• + now fully supporting Unicode! Use all those fancy smileys for your clock text, or tryout other languages like Japanese ;)
• + added update checker checkboxes to about page
• + added link to forums to about page
• * we now call our options, "Options" and no longer "properties" (since that would only apply to single items / files)
• * "removed" Stoic Joker from about page by replacing his logo with mine.. :/
• * context menu slightly reordered
• * hooking is now slightly more safe (when using other 3rd party apps)
• * update checking on first start can be disabled before it triggers
• ! fixed issue on API / DLL shutdown (it didn't correcly wait for DLL to unhook)
• ! fixed .pcb file support. will now play smoothly on Windows 7+
• ! fixed storing of 64bit registry values (thanks B00ze64, #30)
• * other misc changes, tweaks and fixes

for those who like stats

The move from "ANSI" to Unicode increased T-Clocks overall memory usage by about 0.67% with GCC and 0.90% with MSVC.

• GCC: ~5.28 kB (.67%) increase (from 781,311 to 786,590)
• MSVC: ~8.61 kB (.90%) increase (from 959,977 to 968,588)

what this also shows is that our static GCC builds actually use less memory than our MSVC builds (ok I cheated a bit, I've used my local GCC (5.2.0) for testing, which is a lot newer than the one used by Travis (4.6.3) and also "newer" than our MSVC builds (2010))
anyway.. a 5-8 kB increase in memory usage (when it isn't paged) is still quite a lot, yet it's less than 1% of the remaining usage. If paged out memory is also brought into play, the actual increase might be relatively higher but in the end the Unicode build uses not as much of your CPU as it doesn't require Windows to do translations all the time because almost every other app is already using Unicode... It should also increase compatibility with 3rd parties and Windows itself.

To-Do for final release:

• new format option to add "st, nd, rd, th" to current day number eg. September 1st, September 2nd and so forth (requested here)
• import/export tools as well as converter to/from portable
• settings converter should create a backup before converting; less annoying when downgrading (eg. testing a beta build)
• set timezone format?