Closed GoogleCodeExporter closed 8 years ago
Did you modify config.lua?
If so, could you show me your user settings? (first 20 lines of config.lua)
"Xbde not supported, faking double buffer with pixmaps..." is a normal message,
but "lua error config lua:104:attempt to compare nil with number" is not.
I don't have any Windows 7 machine to test with.
Original comment by taesoob...@gmail.com
on 19 Oct 2010 at 5:28
[deleted comment]
I get this same error, using Papercrop 0.43_rev19 on Windows 7 Professional
64bit. I've tried two computers (each 64-bit Windows 7), and get the same error
on both.
Original comment by nkn...@gmail.com
on 10 Jan 2011 at 10:53
Could you try this and let me know the debug output?
print("debug output", pageNo, rectNo, book_pages.nr_of_pages, nr_of_pages_per_pdf_book)
if (book_pages.nr_of_pages < nr_of_pages_per_pdf_book) then
(added one line on config.lua:103)
Thanks,
Original comment by taesoob...@gmail.com
on 10 Jan 2011 at 11:47
It outputs
debug output 0 0 nil 100
lua error lua runtime error
Original comment by nkn...@gmail.com
on 11 Jan 2011 at 1:36
That's really strange. I will take a closer look at it next week.
Original comment by taesoob...@gmail.com
on 11 Jan 2011 at 3:59
Did you use the "process current page" button or "process all pages" button?
At the moment, "process current page" doesn't work with output_to_pdf option.
Thanks,
Original comment by taesoob...@gmail.com
on 22 Jan 2011 at 4:24
I had a similar error on Vista 64. Move the papercrop folder into your Program
Files(x86) folder and it may work. It fixed my problem.
Original comment by bpfist...@gmail.com
on 7 Aug 2011 at 10:31
I installed paperCrop 0.45 rev61 on Win 7 Home Professional 64 bit, and I am
seeing an error similar to the above.
Xdbe not supported, faking double buffer with pixmaps.
pFileName=main.lua
%.lua$ng presets/*.lua
everything is defaulted, no changes.
I tried moving everything to the Program Files(x86) directory, no difference.
Original comment by p...@pwj1s.com
on 14 Aug 2011 at 10:59
I should have added, I am able to process changes, just get the above, but I am
seeing a process blowup on a PDF I was testing with.
Original comment by p...@pwj1s.com
on 14 Aug 2011 at 11:00
I figured out that if I use the Kindle3 as an output device, the blow-up above
goes away. I still get the Xdbe "error" though.
Original comment by p...@pwj1s.com
on 14 Aug 2011 at 11:26
I think I fixed this issue. (Please ignore Xdbe error message that is unrelated
to the problem.) If not, please let me know again using a new issue.
Original comment by taesoob...@gmail.com
on 5 Oct 2011 at 3:10
Original issue reported on code.google.com by
emili.ho...@gmail.com
on 19 Oct 2010 at 3:23