> > I could see some use cases there. My intention was just not to have to set > time/break limits on every open. Another option would be to lazily > initialize those defaults into class vars instead of hardcoding... > > Well my intention also was to provide a way to save preset settings and default settings to external files but again I was distracted by other projects and did not bother implementing this.
Also in process I decided that I did not like the idea of multiple ChronosManagers GUIs to exist, instead I decided to use one GUI to handle multiple timers. This is why I also chose to go down the singleton route , but I gain it fall down the list of priorities because I was busy making CPP . I will be working today to improve ChronosManage, implement the singleton and optimize the loading of its assets because it seems to do some unecessary loading and maybe implement a feature or two. I will keep you posted :)
