Closed GoogleCodeExporter closed 8 years ago
Are you sure, this never happened to me. Please create detailed steps that you
do.
Make sure that the current filter matches the task that you are editing. Also
please
quit the app, reload it and check if the edited time is still in the wrong
place.
Ideally you could attach a demo data file (~/Application
Support/TimeTracker/data.plist) where I can more easily replicate the problem.
Original comment by rbur...@gmail.com
on 12 Apr 2010 at 7:45
ok tried to quit and reload issue is still there
only happen since using 1.3.4 :-(
select a project then select a task and then double click on one of the time
slot
window for editing appear with a dropdown box for task (I like that as i should
be
able to move a time slot to another task if i originally did it wrong).
the current task is ticked , select a task in the list.
the DD box is displayed properly with the task selected , press OK to update.
and it moves it to the task immedialty above the one you select :-)
Original comment by digitalo...@gmail.com
on 12 Apr 2010 at 8:28
Hmm, it works for me, can you be very exact in what you are doing? I.e. are you
editing the currently recording entry? Do you have any filters selected? Please
also
provide screenshots of before, while editing and after.
Original comment by rbur...@gmail.com
on 12 Apr 2010 at 8:43
after more checking it is only happening with the tasks and time block
belonging to
one project.
could it be some data corruption ?
i tried with no fileters so all the tasks from all projects appears and only
the task
belonging to this one specific project do have the issue when updating the time
blocks
is there a databse/file i can send you of my projects/task/timeblock so that
you can
check if there is any issues in it or let me know what to look for ?
Original comment by digitalo...@gmail.com
on 14 Apr 2010 at 1:11
fixed in 1.3.5
Great thanks
Original comment by digitalo...@gmail.com
on 14 Apr 2010 at 5:03
Original comment by rbur...@gmail.com
on 14 Apr 2010 at 8:50
glad to hear
Original comment by rbur...@gmail.com
on 14 Apr 2010 at 8:50
Original issue reported on code.google.com by
digitalo...@gmail.com
on 12 Apr 2010 at 2:42