I'm experiencing this problem in Slickedit 2008 (v 13.0.2).
I tried setting "def_filetouch_checking" to "1", and it doesn't help.
In my case, the file is located on a UNIX server that is shared via SAMBA.
The timestamps between my Windows machine running slickedit, and the UNIX server are very close, within 1 second.
I modify the file in the editor, and save it. After I go and modify some other files, but then come back to this one, it says another application has modified it, which is not true. It is very, very annoying.
Can someone describe how does Slickedit perform the timestamp checking in detail? For example, when a file is saved, does it use the time on the PC that the file was saved as the time to check against? I think it would be smarter for slickedit to perform the following: 1) save the file, 2) retrieve the time stamp from the saved file using the filesystem (such as using the "stat" function in C), and save it, 3) compare the current time stamp of file (using stat function) against the timestamp that was retrieved right after the file was saved.
If I could get this information as how Slickedit determines that another application modified the file, it could help me to find ways to avoid this problem, which is very very annoying when I am editing lots of code, it happens every time I save a file, and I like to save very often.