Reload - Your todo.txt file has been modified by another program.

[BradSherwood]

Issue symptom: Every time I add a new task using jdotxt, I receive a Windows dialog box:
Title: Reload
Message: Your todo.txt file has been modified by another program. Do you want to reload the file?

jdotxt (Version 0.4.5)
Windows 7 Enterprise
todo.txt file is in a folder which is synchronized using Dropbox.
jdotxt autosave is enabled
jdotxt.exe file is dated 6/28/2014 10:51 AM and is 2,249,795 bytes.

Troubleshooting / Additional Information
While my todo.txt file is in a Drobox syncing folder, the symptom occurs even if I pause Dropbox sync.
Even if I both turn off autosave and pause Dropbox, when I save the file, I receive the same Message whenever I save the file.
Uninstalled and Reinstalled - Same Symptom Remained
Tried Run As Administrator - Same Symptom Remained
Tried Run in XP SP3 Mode - Same Symptom Remained
Tried starting new text file in non-Dropbox folder - Same Symptom Remained
Tried starting new text file C:\Users\MyUserName\Documents - Same Symptom Remained

Would appreciate guidance on what to try next.

[kgolding]

I'm getting the same issue, it appears jdotxt is seeing it's own writing to the todo.txt file as an external change. Windows 7 Pro.

[raingros]

Same here!

[joshuatenpenny]

Same here, but it is specific to Dropbox, and does NOT occur when syncing is paused. I do not get this error using Google Drive or saving files locally.

Perhaps a problem with how jdotxt determines whether the file has been changed? Like checking when it was last accessed rather than when it was last modified.

[joshuatenpenny]

WORKAROUND: (At least it works for me.)

Disable autosave in jdotxt settings. Then I only get the error message once when I manually save, instead of repeatedly.

Alternately, I can use something else besides Dropbox to sync. (Which is a pain, because the only reason I was using Dropbox for my todo.txt file is that a bunch of other todo.txt utilities us it.)

[t7ko]

Check out this fork of mine -- https://github.com/t7ko/jdotxt. I made a fix some time ago, and I'm not seeing this issue any more. (I'm checking md5 hash of the entire file before showing the warning.)