matplotlib-devel Mailing List for matplotlib

On Fri, May 09, 2008 at 10:57:09AM -0500, Paul Novak wrote:
> Hello,
> 
> I'm still interested in having a polygon symbol in the legend for a 
> scatter plot. I've made some changes to the suggestion of Manuel Metz to 
> make the legend symbol look better (the code-fragment from legend.py is 
> below). But when resizing the window, the symbol gets stretched and 
> placed in a bad location; it appears that the symbol is stretched and 
> scaled in the same manner as the legend box as a whole, while I think it 
> would look better if the symbol maintained the same size and aspect 
> ratio, but merely moved to the appropriate location within the resized 
> legend.
> 
> I would like to add this functionality, but I need some help to 
> understand the required transformations or scaling to make it look good. 
> Perhaps someone with a better understanding could provide some help?
Even better would be to let the legend be whatever size it needs to
be independent of the scale of the axes. I posted earlier on this
regarding units. 
Sorry, I won't have time to implement this myself.
	 - Paul

Eric Firing wrote:
> Michael Droettboom wrote:
>
>>> I am still having a strange problem: ESP Ghostscript 815.04 (ubuntu 
>>> feisty) chokes on the apostrophe in text, such as in table_demo and 
>>> one or two others. I think this is just a crazy bug in this version 
>>> of gs; you aren't having any such problems, are you? The problem 
>>> does not appear with cairo.ps output because it encodes the text 
>>> strings in some bizarre fashion.
>> Thanks. I've fixed this on the branch and trunk.
>
> Mike,
>
> Thank you--so, is this a workaround for a gs bug, or does the single 
> quote have some special meaning in postscript? When I first ran into 
> the problem I googled and looked at some PS documentation, and I 
> couldn't find anything indicating that the plain single quote 
> character as a literal was forbidden.
0x27 is fine as a literal, but it maps to "apostrophe", not 
"singlequote". The former isn't present in any of the Postscript tables 
of the fonts I looked at (Vera and the standard Windows fonts), so gs 
was crashing on the missing character. So, I just added a line to 
convert all apostrophes to singlequotes. Don't know if that's the right 
thing to do, but it works.
Cheers,
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Michael Droettboom wrote:
>> I am still having a strange problem: ESP Ghostscript 815.04 (ubuntu 
>> feisty) chokes on the apostrophe in text, such as in table_demo and 
>> one or two others. I think this is just a crazy bug in this version 
>> of gs; you aren't having any such problems, are you? The problem does 
>> not appear with cairo.ps output because it encodes the text strings in 
>> some bizarre fashion.
> Thanks. I've fixed this on the branch and trunk.
Mike,
Thank you--so, is this a workaround for a gs bug, or does the single 
quote have some special meaning in postscript? When I first ran into 
the problem I googled and looked at some PS documentation, and I 
couldn't find anything indicating that the plain single quote character 
as a literal was forbidden.
Eric

Hello,
I'm still interested in having a polygon symbol in the legend for a 
scatter plot. I've made some changes to the suggestion of Manuel Metz to 
make the legend symbol look better (the code-fragment from legend.py is 
below). But when resizing the window, the symbol gets stretched and 
placed in a bad location; it appears that the symbol is stretched and 
scaled in the same manner as the legend box as a whole, while I think it 
would look better if the symbol maintained the same size and aspect 
ratio, but merely moved to the appropriate location within the resized 
legend.
I would like to add this functionality, but I need some help to 
understand the required transformations or scaling to make it look good. 
Perhaps someone with a better understanding could provide some help?
Thanks,
Paul Novak
 elif isinstance(handle, RegularPolyCollection):
 if self.numpoints == 1:
 xdata = np.array([left])
 for path in handle.get_paths():
 xy = path.vertices
 p = Polygon(xy)
 x = min(xdata)
 y = y-0.5*HEIGHT
# 0.35 * HEIGHT makes the legend symbol an appropriate size.
# patch_aspect scales the legend symbol to the appropriate aspect ratio.
 patch_aspect = (max(xy[:,0]) - min(xy[:,0])) / 
(max(xy[:,1]) - min(xy[:,1]))
 bbox = Bbox.from_bounds(x, y, 0.35 * HEIGHT, 0.35 * 
HEIGHT * patch_aspect)
 p.set_facecolor(handle._facecolors[0])
 if handle._edgecolors != 'None':
 p.set_edgecolor(handle._edgecolors[0])
 self._set_artist_props(p)
# HERE IS THE ADDITIONAL TRANSFORM FOR THE POLY
 p.set_transform( BboxTransformTo(bbox) + 
p.get_transform() )
 p.set_clip_box(None)
 p.set_clip_path(None)
 ret.append(p)

Eric Firing wrote:
> John Hunter wrote:
>> On Thu, May 8, 2008 at 12:36 PM, Michael Droettboom <md...@st...> 
>> wrote:
>>
>>> Sorry, I mistyped -- it's r5082/r5083. I think those revisions were 
>>> trying
>>> to deal with something more specific to Postscript. Here's the 
>>> commit note:
>>>
>>> "Alternative fix for ps backend bug; removes superfluous 
>>> gsave/grestores."
>>
>> That's the one I am referring to also -- we started talking about some
>> dpi related problems in the thread I referred to and meandered over to
>> this other bug, which was caused by the draw_ps code not properly
>> doing a gsave/restore wrapper if the object did not have a cliprect or
>> a clippath. It was exposed by the quiver key object, which has a
>> collection that uses offsets and no clipping. Eric and I separately
>> committed a patch to make sure gsave/grestore was being called, but
>> his was cleaner so his was the final version. But apparently
>> something was left out...
>
> Yes, I misunderstood something in the original version. I *think* I 
> have it all straightened out now.
Looks good here.
>
> I am still having a strange problem: ESP Ghostscript 815.04 (ubuntu 
> feisty) chokes on the apostrophe in text, such as in table_demo and 
> one or two others. I think this is just a crazy bug in this version 
> of gs; you aren't having any such problems, are you? The problem does 
> not appear with cairo.ps output because it encodes the text strings in 
> some bizarre fashion.
Thanks. I've fixed this on the branch and trunk.
Cheers,
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

John Hunter wrote:
> On Thu, May 8, 2008 at 12:36 PM, Michael Droettboom <md...@st...> wrote:
> 
>> Sorry, I mistyped -- it's r5082/r5083. I think those revisions were trying
>> to deal with something more specific to Postscript. Here's the commit note:
>>
>> "Alternative fix for ps backend bug; removes superfluous gsave/grestores."
> 
> That's the one I am referring to also -- we started talking about some
> dpi related problems in the thread I referred to and meandered over to
> this other bug, which was caused by the draw_ps code not properly
> doing a gsave/restore wrapper if the object did not have a cliprect or
> a clippath. It was exposed by the quiver key object, which has a
> collection that uses offsets and no clipping. Eric and I separately
> committed a patch to make sure gsave/grestore was being called, but
> his was cleaner so his was the final version. But apparently
> something was left out...
Yes, I misunderstood something in the original version. I *think* I 
have it all straightened out now.
I am still having a strange problem: ESP Ghostscript 815.04 (ubuntu 
feisty) chokes on the apostrophe in text, such as in table_demo and one 
or two others. I think this is just a crazy bug in this version of gs; 
you aren't having any such problems, are you? The problem does not 
appear with cairo.ps output because it encodes the text strings in some 
bizarre fashion.
Eric