Swing manages to do this with reasonable results. It essentially passes a custom Graphics2D object through the painting pipeline. The custom Graphic2D operates at printer resolution.
However, there are various pitfalls, including disabling animations, etc. And it tends to flush out more latent painting bugs, because the printer has an effective screen grid of something like (0,0) to (70000, 250000). So it's something that we could probably support, but it would need some work. -- Noel. Niclas Hedhman wrote: > On Wed, Nov 25, 2009 at 6:00 PM, Sandro Martini > <sandro.mart...@gmail.com> wrote: > >> Hi to all, >> I have to prototype a simple Reporting application with Pivot, but one >> of the requirements is to Print the data viewed (in same same way as >> presented, and maybe also in a different way). >> >> Someone has already tried this ? >> Suggestions/problems/pitfalls/comments ? >> > > Typical pitfall; Screen resolution and printer resolution are > typically very different, and since AFAIK Pivot operates on pixels, > this could become a major headache especially in combination with > pixel graphics (if any). > > > Cheers >
