Feature: Autostop timers on obsidan closure

[jimd0t]

Describe the solution you'd like

I find myself leaving timers running when I close my computer, and as I track my work hours I end up having to adjust them on the next day. I think it would be nice to have an optional toggle to auto close running timers.

Technical description

I did some researching on ways to trigger the information update and there are a few options that I can think of.

1. The first option is to use the onunload() event handler.
   This would work on closing obsidian manually, but, on system shutdown it could not work as expected.
2. Create a job that runs every minute that stores the latest save time, then, when obsidian is reopened it would take the latest save time and apply it to any running timer and close them.

Describe alternatives you've considered

I've not found a way of doing this currently.

Additional context

I do understand that not everyone will need this feature, that's why I'm proposing it as an optional toggle in the plugin settings. I know my team uses this plugin for managing tasks and they need to have reports on worked hours so this feature would come in handy for them and I suspect it would be helpful for more users as well.

I'm willing to work on this issue my self.

[jacobtread]

Have read this issue, sounds like a good idea and something I'd be interested in developing myself as It's something I could use as well. Definitely a toggle option though like you've mentioned.

I'm in the process of moving so this issue may take another 2 weeks or so before I can tackle it.

Your every minute background job idea sounds good, it could be good to take a combination of multiple sources here I'll also do some looking into things on my end when I have a chance.

[4Source]

I think the the onunload() approach should work as well, if not better. The scenario in which this might not work is if obsidian crashes (never had that). I also think this is much more performant than doing every minute a file write.

I also would like to see this feature

EDIT: After having a little deeper look in how this plugin works my previous statement is maybe not as important as I thought. I thought the data is stored in a json file in the plugins folder and not in the markdown file it self where obsidian handles the saving (hopefully) performant. Never the less I still think this would be the cleaner solution.

If not going for the onunload() approach I think there should be only one job every minuet (maybe also configurable in the settings so that you have off, 1 min, ...) which is responsible for saving all running timers. If every timer would have it own a lot of timers could still make this slow.