🚀 go-pugleaf

John P. McGrath wrote:
> 
> Ross M. Dukeshier <dukeman@flash.net> wrote:
> 
> > What was meant by JDK v1.1.6 blowing off the JVM?
> > I tested out printing through JBuilder and it worked
> > like a champ.  Is it going to crash my program if I
> > run it outside JBuilder?
> 
> By blowing off, I meant an Access Violation dialog, followed by the
> termination of the "java" or "jre" program.
> 
> I found the problem occurred intermittently, but quite regularly.  As
> I recall, they were more likely to occur when you changed settings in
> the print dialog, such as the page orientation, and when you created
> more than one print job from the same instance of a program.
> 
> There were a large number of bugs reported at the Sun Bug Parade,
> several of them involving blowing off the JVM.  Sun says that these
> bugs were fixed in JDK 1.1.7.  I have tried the program that blew off
> JDK 1.1.6, and it has not done so with JDK 1.1.7, so I presume they
> did fix them.
> 
> --
> Regards,
> 
> John P. McGrath
> <mcgrath@enter.net>
> <jpm@nscs.fast.net>
Thanks for the clarification.  The example I referenced does, in fact,
compute the printable area based on page margin values you pass into it. 

I take it my little one-line print, then, isn't going to give me the
same type of problem you were describing...

I've looked at the JDK 1.2 help for the PrinterJob class.  My
understanding is that this fixes the limitations.  Have you (or anyone
for that matter) tried printing with the new stuff yet?  Just curious to
see if my situation is going to improve...

Thanks 

Ross