Ticket #409 (Fixed)Thu May 21 14:57:03 UTC 2015
Alarm changes DST CMOS settings when its application settings are saved.
| Reported by: | Dick Tanis (1648) | Severity: | Minor |
| Part: | RISC OS: Application | Release: | |
| Milestone: | Status | Fixed |
Details by Dick Tanis (1648):
When saving the Alarm settings via the Alarm Setup window, the DST setting when Alarm has been run is stored instead of the current setting. For example when Alarm is run and the user changes the DST settings from “DST” to “NoDST”. If the user then saves the Alarm settings via the setup window, the DST setting is then reversed back to the value when Alarm has been run. So for this example back to “DST”. This shouldn’t happen. When AutoDST is configured the settings are not changed.
I think there some legacy code there which controls the CMOS DST settings when the Alarm settings are stored because in the old days the DST was also controlled via the Alarm settings window. Nowadays this is not the case so this code should be removed.
Changelog:
Modified by Dick Tanis (1648) Fri, May 22 2015 - 08:25:25 GMT
- Summary changed from Alarm changes DST CMOS settings when it's application settings are saved. to Alarm changes DST CMOS settings when its application settings are saved.
- Release changed from 3rd public site release to Unspecified
Modified by Sprow (202) Tue, June 02 2015 - 19:30:53 GMT
Fixed in Alarm-2_88.
Modified by Sprow (202) Tue, June 02 2015 - 19:31:04 GMT
- Status changed from Open to Fixed
