Fixed timing issue

Finally figured out what the problem was. The calculations by the
algorithm within read task ARE correct -- I'm not crazy. However, when
starting a new task the time written out wasn't the time of writing but
task.startTime which after the initial set of starts/finishes is still
always the original start time. So the sequence file would always have
the start times set as the original start time and not the intermediate
times. This is what caused the strange doubling or exponential growth of
the calculated time.

Now the only problem is that when finishing the time showed is
incorrect. A recurse might fix that.
Fixed Finished task displayed view

Because the endTime was overwritten with current time and the state was
changed to finished, the call to _tc_displayView would show the task
without taking the final segment of the sequence into account.

By setting the task to be in progress and restoring the old endtime
(which would be the prior to finishing seqTime) back to what they were
before writing the task and then calling the view and rendering it as if
it were still running. The total time worked on the task is showne
correctly.