Re: Why does LilyPond delete the PDF first?

[Wilbert Berendsen]

Op woensdag 11 juni 2008, schreef Reinhold Kainhofer:
> Am Mittwoch, 11. Juni 2008 schrieb Carl D. Sorensen:
> > LilypondTool works properly with JPedal under windows.  As long as JPedal
> > is not the active window, the pdf can be properly written.  If JPedal is
> > the active window, then you get a write error on the pdf.
>
> BTW, kpdf works exactly the other way round: Instead of locking the pdf
> file and preventing any changes while the file is viewed, it explicitly
> allows changes while a file is open, watches it and reloads the file if a
> change is detected. This is what lilypond breaks by explicitly deleting the
> file.

I think KPDF doesn't even keep the file handle open after all contents have 
been read and parsed. It just keeps watching the file for changes to its 
mtime, and reopens the file if it is updated. In 
http://code.google.com/p/lilypond/issues/detail?id=635 I added a very small 
patch to scm/backend-library.scm that just deletes the PDF as always when run 
on windows, but not on other platforms.

best regards!
Wilbert Berendsen

-- 
LilyKDE, LilyPond for KDE: http://lilykde.googlecode.com/