matplotlib-devel Mailing List for matplotlib

On 6/20/07, Carl Worth <cw...@cw...> wrote:
> I noticed on the simple_plot.py example that the grid was coming out
> pretty ugly without any snapping on the dashes. Here's a little patch
> that adds that.
>
> -Carl
>
> PS. As should be obvious, this patch depends on my first patch that
> adds the _snap variable.
Steve, I assume you'll handle these?
JDH

I noticed on the simple_plot.py example that the grid was coming out
pretty ugly without any snapping on the dashes. Here's a little patch
that adds that.
-Carl
PS. As should be obvious, this patch depends on my first patch that
adds the _snap variable.

Hm, after I messed around some time with inkscape I finally found a 
workaround - not nice, but it worked - at least for this particular case.
I just copied the plot and pasted it again. Then I could ungroup the 
plot and now inkscape behaved as expected, I still see all my data 
points. Strange enough, inkscape did not change the structure of the svg 
code ...
Norbert Nemec wrote:
> I stumbled over the same problem over and over again, as well.
> 
> I think it is difficult to blame either inkscape or matplotlib. The SVG
> code is correct and Inkscape displays it correctly. The difficulty is
> that the SVG standard does not say anything about the correct *editing*
> behavior. The "ungroup" of inkscape seems to handle the definitions
> within the group that is ungrouped in such a way that the individual
> elements cannot access them correctly any more.
> 
> I think the best fix would be in both, matplotlib and inkscape.
> matplotlib has no need to put the definitions inside the group and can
> simply avoid that, but still inkscape should cope with this kind of
> (legal!) SVG code in a better way.
> 
> 
> 
> Manuel Metz wrote:
>> Hi,
>>
>> I have a problem with the svg output of matplotlib. I created a
>> scatter plot and saved it to svg. For the scatter plot I used two
>> kinds of symbols to mark different types of data. Afterwards I opened
>> the file using Inkscape to make some minor modifications. When opening
>> the file it looked fine (see Screenshot1.png). However, to do the
>> modifications I had to 'ungroup' the axis. After that one group of the
>> two markers disappeared from the plot (see Screenshot2.png). The data
>> is however not deleted, it's just invisible in Inkscape (but not in
>> Firefox ;-).
>>
>> I suspect it has to do with the clipPath definition, which is defined
>> for the regpolycollection4 (the green triangles, which are plotted
>> first) but not for the regploycollection5 (the blue dots, which are
>> plotted second).
>>
>> Is there any reason why a clipPath is defined for only one of the
>> Collections? I'm not sure whether this is a bug in matplotlib svg
>> output or Inkscape, but naively I would say that Inkscape behaves
>> correct here.
>>
>> Hope this can be fixed,
>> Manuel
>>
>> Uuuu, btw. I'm using matplotlib 0.90.1
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
---------------------------------------
 Manuel Metz ............ Stw@AIfA
 Argelander Institut fuer Astronomie
 Auf dem Huegel 71 (room 3.06)
 D - 53121 Bonn
 E-Mail: mm...@as...
 Web: www.astro.uni-bonn.de/~mmetz
 Phone: (+49) 228 / 73-3660
 Fax: (+49) 228 / 73-3672
---------------------------------------

The draw_arc code was putting all arcs centered on the origin instead
of the proper location. This patch fixes that.
With this, plus my earlier patch #2 to enable clipping, the
line_styles.py example is now rendering quite well with the cairo
backend.
However my patch #1 to add the snapping is messing up line_styles in
some places. For example, where there is a strokes sine wave the
snapping is interfering with its proper shape.
Obviously, snapping smooth, curved user data being plotted like that
is a really bad idea. Things that should be snapped are things like
frames, grid lines, ticks, and object borders, particularly when
aligned with an axis.
-Carl

Here's a second[*] patch for the cairo backend.
This one re-enables clipping. All the necessary code was present
already, but disabled with a comment claiming problems on two of the
examples. I double-checked both examples but found no problems,
(whereas, obviously without clipping things don't work at all after
panning/zooming).
-Carl
[*] Apparently my first patch hit the list before my subscription
request was completely processed. So it's either been queued up for
moderation or deleted by now. Please let me know if I should re-send
it.