Duncan,
Clearly, you're a better man than I am; I could never get through any Knuth section in 25 minutes.
Let's talk about how this might work. Knowing that it has "potentially timed out", TT would have to cache the time at which it thought it timed and instead continue to accumulate time. It would also have to display a dialog to let the user know they have a choice. Upon making the choice either the record is left alone and running (not accepting the timeout) or the record is sliced off by the difference between the record time and the cached time. If the dialog is being displayed, the user can't alter the start time, so there shouldn't be any weirdness with altering the time to before the start of the timeout. Most of the machinery for this is already in place (timeout mechanism, adjusting record end times at stop, etc.).
A persistent setting will have to be added to the configuration (takes about 15 minutes from GUI to persistence including the version check for backwards compatibility). The biggest part will probably be the testing.
I'll add it to the mod list for the next release. It may not make the cut, but it looks like something that would probably get into the application.
Thanks,
james
P.S. I didn't realize anybody was actually using the "Idle Timeout" feature. I guess we may have to revisit the decision to cull it from the Time Tracker Multi-User version.
james