|
From: | Rick M. Cox |
Subject: | RE: Help with saveas and fltk |
Date: | Sat, 15 Jun 2013 21:15:02 -0700 |
From: Michael Goffioul [mailto:address@hidden On Sat, Jun 15, 2013 at 12:12 PM, Dmitri A. Sergatskov <address@hidden> wrote:
That's indeed something I have been wondering. For the record the way printing from FLTK/OpenGL works is as follows: 1) the OpenGL feedback buffer is turned on 2) octave makes the plot by sending all the required OpenGL commands 3) GL2PS retrieves the feedback buffer from OpenGL; this buffer contains the list of primitives representing the plot; those primitives are expressed screen coordinates (basically the buffer contains the 2D projection of the 3D scene) 4) GL2PS translates the primitives into equivalent PostScript commands The point is that the content of the buffer in 3) is driver dependent. If you have spurious lines in the final postscript file, it can mean that: 1) GL2PS is buggy and misinterpret the content of the feedback buffer 2) the driver is buggy and put unwanted primitives in the feedback buffer Michael. I’m happy to run any experiments or provide any information that you might need to run this idea down further. Rick |
[Prev in Thread] | Current Thread | [Next in Thread] |