I think it is a good idea to add such a feature in mpl, and I guess it
would better to have some general way to provide backend specific
options.
Actually, I have been using a modified version of mpl which enables to
set the individual ID of the patches (this is only meaningful in case
of the svg
Hello,
I have been putting some initial effort on implementing a new Legend
class which has paddings in canvas unit.
A related post is
http://www.mail-archive.com/[EMAIL PROTECTED]/msg08560.html
My current implementation has a same functionality as the old one (an
example figure attached), but
On Thu, Oct 30, 2008 at 2:59 AM, Jae-Joon Lee [EMAIL PROTECTED] wrote:
Basic idea is to create a new version of the Legend class with a same
interface to the current one.
Eric's original suggestion was to use some optional kwarg to choose the
version.
But I found this approach does not work
Agreed. I think it is missing only be accident.
Mike
John Hunter wrote:
On Wed, Oct 29, 2008 at 4:00 PM, Ryan May [EMAIL PROTECTED] wrote:
Here's probably a better question to ask than just to fix the example.
Was it intended that the Rectangle.xy attribute disappear? I couldn't
find
Jae-Joon Lee wrote:
I think it is a good idea to add such a feature in mpl, and I guess it
would better to have some general way to provide backend specific
options.
Also note that this specific functionality isn't backend-specific. PDF
files, for example, also have the ability to have
On Thu, Oct 30, 2008 at 12:32 AM, Jae-Joon Lee [EMAIL PROTECTED] wrote:
John and others,
I submitted a patch of the fancy arrow I mentioned a while ago.
http://sourceforge.net/tracker2/?func=detailaid=2209021group_id=80706atid=560722
Hi Jae Joon -- sorry for not responding. I had completely
On Thu, Oct 30, 2008 at 8:10 AM, Michael Droettboom [EMAIL PROTECTED] wrote:
In the specific case of bar(), one may still be forced to manually set
urls on each Rectangle if one wants those urls to be different. But
this is no different than the current situation wrt facecolor or any
other
Another use case in favor of implementation of the URL property at the
artist level:
Consider a map with scatter points representing geolocated photos that
can be viewed at some URL. Attach a mouse click on the artist to the
following code:
import webbrowser
webbrowser.open(patch.url)
And you
Line 2900 in patches.py is not compatible with python-2.6. as is protected
and cannot be used as a variable name.
On Thursday 30 October 2008 09:49:24 am John Hunter wrote:
On Thu, Oct 30, 2008 at 12:32 AM, Jae-Joon Lee [EMAIL PROTECTED] wrote:
John and others,
I submitted a patch of the
On Thu, Oct 30, 2008 at 9:28 AM, Darren Dale [EMAIL PROTECTED] wrote:
Line 2900 in patches.py is not compatible with python-2.6. as is protected
and cannot be used as a variable name.
good catch - -fixed in r6355
JDH
-
All (with a special hello to Jeff W.),
I'm running into a problem with the latest basemap (r6355), illustrated in the
following. Looks like the resolution 'i' causes a TopologyException
GEOS_ERROR: TopologyException: found non-noded intersection
between -42.7171 -2.56422, -42.7313 -2.57589
and
Pierre GM wrote:
All (with a special hello to Jeff W.),
I'm running into a problem with the latest basemap (r6355), illustrated in
the
following. Looks like the resolution 'i' causes a TopologyException
GEOS_ERROR: TopologyException: found non-noded intersection
between -42.7171
I realised in my earlier message, I didn't really address your initial
request for feedback on your approach.
I think the goal here should be to make the url support as pervasive as
possible wrt both plot types and backends.
Many of the high-level plotting functions (such as bar()) take a
13 matches
Mail list logo
