New backend API

Development matplotlib-devel
#1

   double lastx(-2.0), lasty(-2.0); @@ -1339,9 +1341,15 @@

    > }
    > catch (...) { moveto = true; + skippoint = true;
    > continue;
    > }
    > - + else + if (MPL_isnan64(thisx) || MPL_isnan64(thisy)) {
    > + moveto = true; + skippoint = true;

I don't think you need skippoint. A combination of setting "moveto"
with "continue" should suffice. continue implicitly skips the point,
and setting the moveto flag indicates to agg not to connect the
previous with the next point.

   catch (...) {
        moveto = true;
        continue;
       }
    else
      if (MPL_isnan64(thisx) || MPL_isnan64(thisy)) {
        moveto = true;
        continue;
      }

JDH

#2

I'm having second thoughts about the wisdom of having postscript handle the
transforms. With the new API, I run backend_driver.py and get a file called
axes_demo_PS.ps. On my machine, it takes about 10 seconds to open this file
if it was created with the new API. If I mask draw_markers and recreate the
postscript file, it loads instantly.

Any thoughts?

#3

Let me make a correction. Viewing the file should not take so long, but there
is something strange going on that I dont understand. axes_demo_PS.ps
actually takes almost a full minute to load on my computer if the new API is
used (excuse my first incorrect report). What I see is that the blue line is
immediately rendered, and then ghostscript seems to stall for 45 seconds, and
then renders the rest of the file. If I comment out the blue line in the
postscript file itself:

% gsave
% 446.4 345.6 72 43.2 clipbox
% [446.4 0 0 6920.64 72 159.326] concat
% 0 0.001725 m
[...]
% 9.999 -4.733e-05 l
% gsave 0.00224014 0.000144495 scale stroke grestore
% grestore

then the file will load immediately, with no pause. This is strange, I cant
identify the source of the hangup.

Darren

···

On Monday 03 April 2006 11:00, Darren Dale wrote:

I'm having second thoughts about the wisdom of having postscript handle the
transforms. With the new API, I run backend_driver.py and get a file called
axes_demo_PS.ps. On my machine, it takes about 10 seconds to open this file
if it was created with the new API. If I mask draw_markers and recreate the
postscript file, it loads instantly.

Any thoughts?