Messages - bobofeta [ switch to compact view ]

Pages: [1]
1
If you develop for a platform, you know that the platform's developers are under no obligation to support your software.  Or at least you should know that.  You have to roll with the platform's releases.  They didn't intentionally break t-clock.  They also didn't intentionally not break it these years.  It would be up to a developer to figure out what the problem is, and change/correct the software.

Exactly.

This is standard software development. Developers usually have to update their software for new releases.

For example, if you wrote a program that ran on Mac OS X Tiger, don't assume it will still run on macOS Sierra.

2
I don't think it's a bug, and I don't think this is a case of just wait until Microsoft fixes it. It's really just a heads-up to the dev that the Creators Update changes some things. This seems to be typical of Windows 10 major releases. It happened with the Windows 10 November Update, the Windows 10 Anniversary Update and will probably happen again with the upcoming Windows 10 Redstone 3 Update. These are very different operating systems. It's just Microsoft's decided to call them all Windows 10 and finally give updates away for free like everyone else is doing. But some low level, third party apps have to be adjusted.

Also, the recent WannaCry ransomware virus is a healthy reminder to keep your systems updated.

And the "Display Properties' shortcut in T Clock certainly isn't a high priority deal-breaker...

3
IainB, it doesn't look like you're running the Windows 10 Creators Update. It was just rolled out recently. If Windows Update says "you're up to date", there should be a message underneath that text explaining how to download the Creators Update from Microsoft.

4
t-clock error.png

Windows 10 Pro • 64-bit • Version 1703 • OS Build 15063.296 • (Creators Update)

Pages: [1]
Go to full version