I received some interesting feedback about the Screen Timeout Tool I wrote for Android.
One of the most interesting feedback is one telling me that the timeout setting does not persist. Any application that runs on the Android can change the timeout setting, provided they know what, where and how to change it.
Given a television with a single remote controller and multiple people who can access the controller, the channel on the TV you've selected using the remote controller could be changed by anyone who touches the controller.
And it's the same with the screen timeout setting. Instead of thinking things through, this user sent me an email blaming me.
In 2017, with the release of Delphi 10.2 Tokyo, Embarcadero introduced a specialized implementation of the Observer pattern into the System.Classes unit. While it has been in the wild for 9 years, it remains a "hidden" architecture for many, primarily because it serves as the invisible engine behind LiveBindings. Other than live bindings, you can also use the Observer pattern as a way to update component settings to the Windows registry, an .ini file, or persist it elsewhere.
System.Classes