1

Resolved

Stop the Clock Status Should be Persisted

description

If I stop the clock, exit the application and then restart it, the I am prompted to 'Stop the Clock' again. The fact that the clock is stopped should be persisted to the data store.

comments

nootn wrote Aug 17, 2008 at 10:44 AM

I think that you are right, what it does at the moment is always brings up the last entry you put in whenever you open it.

However, this is very annoying, because in the normal case, you close the application at the end of a day and start it again another day, so by bringing back the last time you may forget the time you finished.

So, I think that to cover the common scenario, taking out the memory all together (just always start with the clock stopped) is the best way.

I have done this for the next release. Let me know if you have any other thoughts on this.

wrote Aug 17, 2008 at 10:44 AM

samunro wrote Aug 18, 2008 at 10:40 AM

This solution is not optimal where I exit the application during the day (to install a new release for example). Despite not having clicked 'Stop the Clock' the entry that I was working on is closed after I restart the application. I don't have any easy way to continue this entry.

I think that persisting the state of the clock would be a better solution.

nootn wrote Aug 21, 2008 at 1:35 PM

Fixed for next release (0.005) or in latest source code. You will need a new config entry for it to work:
<add key="LocalSettingsFile" value="LocalSettings.xml"/>

wrote Aug 21, 2008 at 1:35 PM

wrote Feb 12, 2013 at 7:43 PM

wrote May 14, 2013 at 5:40 AM

wrote May 14, 2013 at 5:40 AM

wrote Jun 6, 2013 at 12:40 AM