I have just installed KDE on Windows 4.10.2 (which is amazing, by the way) through the installer. I set up kile and okular and everything works fine except the live preview.
Firstly I was getting

Code: Select all

[Kile] Unknown tool LivePreviewPDFLaTeX

error, which I was able to fix with "Restore Default Tools..." option.

Now I am getting the following error when I open a .tex file with livepreview enabled:

Code: Select all

*****
*****     LivePreview-PDFLaTeX output:
*****     cd "C:/Users/joon/Dropbox/Project/paper"
*****     pdflatex -synctex=1 -interaction=nonstopmode -output-directory=C:/Users/joon/AppData/Roaming/.kde/share/apps/kile/livepreview/preview-2Xbaaa/ master-tables.tex
*****
This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/W32TeX)
 restricted \write18 enabled.

entering extended mode
! I can't find file `master-tables.tex'.
<*> master-tables.tex
                     
(Press Enter to retry, or Control-Z to exit)
Please type another input file name
! Emergency stop.
<*> master-tables.tex
                     
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on C:/Users/joon/AppData/Roaming/.kde/share/apps/kile/livepr
eview/preview-2Xbaaa//texput.log.


And indeed, if I go the to directory, I only see texput.log there.

How should I fix this?

Is the name of this TEX file "master-tables.tex" by any chance?

bcooksley wrote:Is the name of this TEX file "master-tables.tex" by any chance?

Yes it is.

I am not sure if livepreview really works on windows, there is a bug in several windows applications that the files cannot be renamed/removed/regenerated while the app is still opened. I think this also breaks live preview and the symptoms you see here are misleading.

SaroEngels wrote:I am not sure if livepreview really works on windows, there is a bug in several windows applications that the files cannot be renamed/removed/regenerated while the app is still opened. I think this also breaks live preview and the symptoms you see here are misleading.

Thanks. Then I will wait for the next update and see if it gets fixed.