Comment disappears after about 20 secs

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enter any Text in the comment field.
2. Wait some seconds and the text will vanish. 
3. A work around for this is to hit enter before the text disappears.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Kronox 1.0b with OS X 10.6.2

Please provide any additional information below.

Original issue reported on code.google.com by Sollberg...@gmail.com on 18 Feb 2010 at 8:53

[GoogleCodeExporter]

After some limited testing, I have failed to reproduce this so far on Kronox 
1.0b with OS X 10.6.2.  Does this 
happen on New and Edit, and with finished tasks or ones which are still running 
…?

Original comment by the...@gmail.com on 21 Feb 2010 at 10:29

[GoogleCodeExporter]

Ok, I found out when this issue appears...

1. Open a new task and start writing the comment.
2. Change the date of the task
3. The text which is entered after the date change will vanish if you don't hit 
enter

Original comment by Sollberg...@gmail.com on 25 Feb 2010 at 7:44

[GoogleCodeExporter]

Okay, got it. 

I thought I solved that problem...

Original comment by peter.ljunglof@heatherleaf.se on 15 Mar 2010 at 6:50

• Changed state: Accepted

[GoogleCodeExporter]

Was this fixed in r81 (KronoX version 1.0b2)?

Original comment by peter.ljunglof@heatherleaf.se on 13 Apr 2010 at 8:37

[GoogleCodeExporter]

Following steps in Comment 2 I can't get this error to appear.

Original comment by the...@gmail.com on 13 Apr 2010 at 10:21

[GoogleCodeExporter]

I've been using 1.0b2 for a while and it happened to me once. I'll try to 
reproduce it more reliably.

Original comment by hsoft@hardcoded.net on 7 Apr 2012 at 7:23

[GoogleCodeExporter]

I can reproduce regularly, but not so regularly. The best method of reproducing 
the issue I've found so far is to start a running work period, start editing 
the comment field, and focus on another app by clicking on it. Half the time, 
you would lose your comment edit.

Original comment by hsoft@hardcoded.net on 7 Apr 2012 at 8:17

[GoogleCodeExporter]

r91 Fixed the problem I was able to reproduce. With some luck, that nailed it.

Original comment by hsoft@hardcoded.net on 7 Apr 2012 at 9:07

[GoogleCodeExporter]

I messed up in r91 and introduced another bug, which is that any edit in the 
work period will cause the widget that currently has the focus to lose it. That 
makes manual time editing particularly arduous.

I reverted that fix and introduced a better fix in r46253028a6f4 which simply 
makes the binding of the comment field continuously update. I did a lot of 
messing around in the code before choosing that solution, and it's the less 
glitchy one.

The real problem is the timer that regularly calls "saveManagedObjectContext:" 
in Krono.m:awakeFromNib. I think it should be removed, but I'm not sure of the 
implications of doing it, so I don't dare doing so in a bugfix release.

Now, we still have a glitch that whenever saveManagedObjectContext:, our 
currently focus widget in the work panel loses focus. It's annoying, but we 
don't lose editing anymore.

Original comment by hsoft@hardcoded.net on 10 Apr 2012 at 6:18

[GoogleCodeExporter]

I removed the call to save the database every 30 seconds which is the root 
cause of this problem in rc705fabd51bc . Because I don't know why it was 
originally, it's possible that this removal brings other problems, but so far 
I'm not aware of these problems, so I guess they're rather minor. I'll deal 
with them when they arise (with, hopefully, a better solution). Until then, 
this ticket is fixed.

Original comment by hsoft@hardcoded.net on 18 May 2012 at 1:20

• Changed state: Fixed

[GoogleCodeExporter]

As I recall I added the autosave as a precaution -- if the computer would hang 
or something. But if removing it solves this issue, I'm all in favor.

Original comment by peter.ljunglof@heatherleaf.se on 20 May 2012 at 6:59