@Izidor I totally agree with you, that would be the most straightforward behavior:
1) I check gtg to check what task to work on now (thats what gtg is for, isn t it?)
2) i click the track-in-hamster-button
3) as soon as i mark it as done, tracking is stopped and i go back to (1)
It already works very well, because i only have to stop the last task i work on, because subsequent "track-in-hamster" clicks do stop the tracking of the last and start tracking of the current one.
Jim's proposal seems to me very sophisticated. I'd use the feature the described way, and i would file a bug if gtg started some other activity in hamster on marking a task as done
@Izidor I totally agree with you, that would be the most straightforward behavior:
1) I check gtg to check what task to work on now (thats what gtg is for, isn t it?) hamster- button
2) i click the track-in-
3) as soon as i mark it as done, tracking is stopped and i go back to (1)
It already works very well, because i only have to stop the last task i work on, because subsequent "track-in-hamster" clicks do stop the tracking of the last and start tracking of the current one.
Jim's proposal seems to me very sophisticated. I'd use the feature the described way, and i would file a bug if gtg started some other activity in hamster on marking a task as done