On Tue, Sep 26, 2006 at 08:43:14AM +0200, Georg Baum wrote: > Enrico Forestieri wrote: > > > Whatever the cause, it is becoming really annoying. > > That sounds like a reasonable explanation. What I do not understand at all > is why yap needs to lock the file. xdvi on linux is perfectly capable of > monitoring files without lock, so why does this not work on windows? Or do > they want to mimic adobe reader???
You cannot avoid to lock a file when you access it on Windows. Maybe yap accesses briefly the file even when its window is not active and this can happen right when some other program wants to overwrite it. So there is a race and sometimes it goes well but not always. I think that in 2.4 yap was checking the file only when its window was active, such that the race was avoided, but I don't know for sure as I never had a look at the sources. On the contrary adobe reader opens the file and never closes it. As I said you don't need to explicitly lock a file on Windows and that is why you need to reboot so often when you perform an upgrade, as objects in use cannot be replaced... > Somebody should take this to the author of yap. Indeed. Uwe, I think you are in contact with him? -- Enrico
