octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44125] mxe-octave: fltk printing displays lin


From: Rik
Subject: [Octave-bug-tracker] [bug #44125] mxe-octave: fltk printing displays line dropouts in dev version
Date: Mon, 02 Feb 2015 17:03:08 +0000
User-agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1)

Update of bug #44125 (project octave):

                  Status:                    None => In Progress            

    _______________________________________________________

Follow-up Comment #7:

What are the performance implications of just using GL2PS_BSP_SORT all the
time?

According to the documentation for gl2ps:


Specifies the sorting algorithm, chosen among:

GL2PS_NO_SORT
    The primitives are not sorted, and are output in stream in the order they
appear in the feedback buffer. This is sufficient for two-dimensional scenes.
GL2PS_SIMPLE_SORT
    The primitives are sorted according to their barycenter. This can be
sufficient for simple three-dimensional scenes and/or when correctness is not
crucial.
GL2PS_BSP_SORT
    The primitives are inserted in a Binary Space Partition (BSP) tree. The
tree is then traversed back to front in a painter-like algorithm. This should
be used whenever an accurate rendering of a three-dimensional scene is sought.
Beware that this algorithm requires a lot more computational time (and memory)
than the simple barycentric sort. 


I changed from NO_SORT to SIMPLE_SORT to correctly handle the 'layer'
attribute for axes (either in front of or behind the 2-D objects on the
screen).  I would think that most of the time the GL2PS_BSP_SORT wouldn't
actually be much more time consuming for your average 2-D plot.  However,
there are probably some situations, like a scatter plot with 99 points, which
might show a difference.

If benchmarking doesn't show much of a change I would be fine changing the
default to BSP_SORT.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44125>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]