Mathis Dirksen-Thedens

I already tried to display something more meaningful when I built the tile some time ago, but the tile wouldn't update reliably. So I figured it would be better to...

@WildOrangutan If you want a big task, you could revive #23 and introduce a database framework. But, on the other hand, I don't know exactly if that would fix the...

Another possible way would be to hold only the task used for the last clock-in inside a variable (only for this use case). If the variable is `null`, the current...

That's right, in this issue it's only planned to have multiple work locations for the same employer. The time clocked at any of the locations should count for this one...

@HerHde I just added #197 for tracking the "multiple employer" situation you asked about. I have two jobs myself and already thought about tracking both in one TWT instance, but...

Thanks for this feature request. I also had to enter my time in 15 minute chunks, both in my previous day job and in my current one, and up to...

Thanks for your idea! It sounds promising, especially the visualisation may help some people. As for the backup without Google, there's a relatively easy workaround. The app creates a backup...

Thanks for your ideas! I think the UI indded could be designed better, from my viewpoint there could be a widget (maybe another one while keeping the current one unchanged?)...

A new event is not unlabelled, it uses the default task. And perhaps a carousel/spinner for the tasks makes sense in a new widget - this way a popup for...

Maybe the app could also do some simple math on clock-in: if a (non-default) task is selected ten times in a row on clock-in, the user is asked if this...