On Monday 10 September 2007, Hal Vaughan wrote: > Sorry to post an obnoxious "Urgent" comment in the header, but I'm > online with a client's computer through VNC and if it's at all > possible I need to resolve this problem while online. ... > I think I've been told, and likely here, that in 2.0.x, print > listeners like this are no longer necessary, but I'm having a bit of > a problem searching and finding this comment and what the background > is. > > In 2.0.x, can I print, then close the document without listening for > when the print job is done? Can someone confirm this for me? I've > been stuck on this problem for about a month (I thought it was other > possibilities, and had another couple issues as well) and I'm at a > point where I need to solve it and my client is, understandably, > anxious about it.
I've found I *have* to have a print listener and watch for when the document is done printing. Here's more detail on what's happening (sorry for things being fragmented, but I'm under tremendous pressure to solve this). This is happening on a Windows XP system with 2 CPUs. I was using Java 6 but now I'm using Java 5 and that makes no difference. I have my own Windows XP system but I cannot duplicate the problem on my computer. This only happens when printing multiple files. Sometimes it happens after I print 2-3 files, sometimes it happens after 50 or more files. There's no pattern to how many files it has to print before there's a problem. When I get a problem, I get the OOo "File Corrupt" window saying there is a problem with a file and it will try to restore it the next time OOo starts. If I start OOo, I get an empty file in Writer, as always, but I don't get any file to restore. I suspect I'm getting an error with the null file after closing or something like that. I am NOT getting errors reported in Java from this. If I click on the "Okay" button on the error window, then my system keeps running but isn't able to load a file. At this point it's a bit confusing because I have to go through old code I haven't read in a year. What can make OOo, while being run from Java, report a bad file and NOT throw a Java error? Again, thanks for any insight on this! Hal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
