Re: [Gimp-print-devel] Printing RGB layers in B&W.

[Keith P. <em...@mt...>]

   Date: Tue, 29 Feb 2000 19:07:03 -0500
   From: Robert L Krawitz <rl...@al...>
   
      Date: Tue, 29 Feb 2000 21:42:31 +0000 (GMT)
      From: Keith Parks <em...@mt...>
   
      I have a peculiar problem with the latest CVS versions of the
      print plugin and gimp.
   
   Is this the CVS version of the print plugin from the Gimp source
   (3.0.x) or from the gimp-print source (3.1)?

Both the version with Gimp and the standalone exhibited the same
behaviour with RGB layered imaged.

I did a "cvs update" on the gimp yesterday ans rebuilt the Gimp
overnight (That's how long it takes!!).

Now the Gimp version of print just appears to hang with "Printing..."
on the progress bar. When I cancel the Gimp bombs out.
    
      If I create a new RGB image in Gimp, add a new layer and then
      scribble something on it, when I come to print I get an odd
      behaviour.
   
      The multi layer is detected and the export/merge-visible dialogue
      activated. I accept this and am presented with the new print
      dialogue.
   
   Does this happen with a non-layered (but still RGB) image?  If it
   happens only with a layered image, it sounds like the problem is with
   the Gimp.  If it happens with any kind of RGB image (or it varies with
   the kind of image, indexed behaves differently from RGB for example)
   it may be a problem with the plugin.

Single layer RGB and Indexed (multi and single layer) are OK.

If I merge in Gimp before printing it fails in the same way.
If I flatten in Gimp before printing the output is OK.

A layered RGB image, saved as a .png, calls the export routine to
merge the layers and the saved image is OK when viewed in Netscape.
 
   Also, did this just start?

I'm not sure, all my printing of recent times has been of scanned
images, which have all been single layer.

It's odd the image always displays OK even when merged. It only
seems to be the Postscript printed output that's wrong.

Thanks for your interest.

I'll continue to play and see if I can locate the problem.

Keith.