Currently (due to the way it is persisted), the Timer class can only safely support one instance per context. This makes it effectively a singleton, although it is possible that future versions of Clock may call for multiple timers. Re-structure the Timer code to support an arbitrary number of instances, and move the assumptions about number of Timers to higher-level application logic (avoiding the use of global variables where possible).
(bug cleanup: if we support multiple timers in a future Clock version, we can modify the Timer class accordingly.)
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.