Carl Worth wrote:
don't think it is supported in cairo. So I am not sure where these
rasters are coming from, unless cairo is converting all text to
rasters.
Definitely not converting all text to raster, (unless someone's using
an ancient version of cairo).
I don't know the root
I had no trouble reproducing this on my Ubuntu Feisty box.
It turns out that wxPython leaks a dictionary for every object whose
class subclasses a Wx class. There is a fix for this that made it into
wxPython-2.8.3.0:
On 7/6/07, Michael Droettboom [EMAIL PROTECTED] wrote:
I don't know the root cause, but FYI I'm definitely getting rasterized
text with the Cairo backend for mathtext_demo.py. (I'm using
cairo-1.4.10, which I believe is the latest stable release).
And you are pretty sure it is all the text,
I had no trouble reproducing this on my Ubuntu Feisty box.
It turns out that wxPython leaks a dictionary for every object whose
class subclasses a Wx class. There is a fix for this that made it into
wxPython-2.8.3.0:
I had no trouble reproducing this on my Ubuntu Feisty box.
It turns out that wxPython leaks a dictionary for every object whose
class subclasses a Wx class. There is a fix for this that made it into
wxPython-2.8.3.0:
I had no trouble reproducing this on my Ubuntu Feisty box.
It turns out that wxPython leaks a dictionary for every object whose
class subclasses a Wx class. There is a fix for this that made it into
wxPython-2.8.3.0:
My sincere apologies for the multiple copies of the e-mail sent this
morning. I was getting SMTP server down messages, but clearly the
messages were sent anyway.
I'm not a spammer, really! ;)
Mike
-
This SF.net email is
On Friday 06 July 2007 08:35:31 am John Hunter wrote:
On 7/6/07, Michael Droettboom [EMAIL PROTECTED] wrote:
I don't know the root cause, but FYI I'm definitely getting rasterized
text with the Cairo backend for mathtext_demo.py. (I'm using
cairo-1.4.10, which I believe is the latest
I had no trouble reproducing this on my Ubuntu Feisty box.
It turns out that wxPython leaks a dictionary for every object whose
class subclasses a Wx class. There is a fix for this that made it into
wxPython-2.8.3.0:
I had no trouble reproducing this on my Ubuntu Feisty box.
It turns out that wxPython leaks a dictionary for every object whose
class subclasses a Wx class. There is a fix for this that made it into
wxPython-2.8.3.0:
I had no trouble reproducing this on my Ubuntu Feisty box.
It turns out that wxPython leaks a dictionary for every object whose
class subclasses a Wx class. There is a fix for this that made it into
wxPython-2.8.3.0:
On 7/5/07, Carl Worth [EMAIL PROTECTED] wrote:
Thanks, John, for sharing this essay. Please allow me to respond to a
few points:
Hey Carl -- thanks for the response. You have definitely made me
reconsider some of my arguments, though my conclusion mostly remains
intact. At the end of the
John Hunter wrote:
What about simple_demo.py -- do you get rasters there too?
No. I get vectors there.
I noticed that using the backend GtkCairo seems to use backend_ps.py
for Postscript output. Using backend Cairo uses cairo. Maybe
probably explains the difference between Darren and my
Hi,
I've been playing with the pick infrastructure in 0.90 and find that
it doesn't meet my needs. The issue is that events from all artists
go to the same callback, so you are forced write your callback as a
series of if statements for each artist which may receive a pick event.
I would rather
On 7/6/07, Paul Kienzle [EMAIL PROTECTED] wrote:
Hi,
I've been playing with the pick infrastructure in 0.90 and find that
it doesn't meet my needs. The issue is that events from all artists
go to the same callback, so you are forced write your callback as a
series of if statements for each
On Fri, Jul 06, 2007 at 10:15:48AM -0500, John Hunter wrote:
On 7/6/07, Paul Kienzle [EMAIL PROTECTED] wrote:
Hi,
I've been playing with the pick infrastructure in 0.90 and find that
it doesn't meet my needs. The issue is that events from all artists
go to the same callback, so you are
On 7/7/07, Christopher Barker [EMAIL PROTECTED] wrote:
Sorry to spam this list with this, but it came up here...
Carl Worth wrote:
http://www.scipy.org/License_Compatibility
Thanks, John, for sharing this essay. Please allow me to respond to a
few points:
I can't answer your question
On Sat, 7 Jul 2007 02:16:34 +0900, Bill Baxter wrote:
Carl Worth wrote:
http://www.scipy.org/License_Compatibility
Thanks, John, for sharing this essay. Please allow me to respond to a
few points:
I can't answer your question about GPL in the gub'ment, but I would really
like to
Cheat commandos, Rock rock on.
Sounds great. This is sorely needed in matplotlib I think. But I have no
idea how to make it work. Mayavi is way to huge for the kind of simple 3D
plotting needs most folks have.
--bb
On 7/7/07, Nicolas Rougier [EMAIL PROTECTED] wrote:
Hi all,
I've been
On Fri, 6 Jul 2007 08:20:59 -0500, John Hunter wrote:
On 7/5/07, Carl Worth [EMAIL PROTECTED] wrote:
Hey Carl -- thanks for the response.
You're quite welcome. Thank you for receiving it as intended---as an
alternate viewpoint based on my experience.
I think LGPL is a perfectly good license
On Fri, 06 Jul 2007 10:05:22 -0700, Christopher Barker wrote:
Sorry to spam this list with this, but it came up here...
Carl, you have clearly thought this out a lot, and have a real
experience with this, so I have a issue that you may have some insights
into:
Yes, I have thought about
All,
I am reviving this old thread because the topic came up in a thread with
a less-apropos name, and I think we can move it forward a bit more now.
Steve's message (below) is still a useful summary of the cairo status.
examples/backend_driver.py can now be used for wholesale testing and
On 7/6/07, Eric Firing [EMAIL PROTECTED] wrote:
2) polar_demo.py: the part of the spiral outside the bounding circle is
removed in the Agg version but not in the Cairo version.
This is a fairly new feature I added to add -- clipping to a polygon.
I haven't ported it to postscript yet. The
Carl Worth wrote:
Yes, I have thought about licensing a lot. And I'll gladly share my
opinions, (but no legal advice, of course, etc. etc.).
Thanks for your input.
I work for the US federal government, and we are not allowed to
copyright our work, so be definition, any code we write is in
On Fri, Jul 06, 2007 at 10:15:48AM -0500, John Hunter wrote:
On 7/6/07, Paul Kienzle [EMAIL PROTECTED] wrote:
Instead I would like to start by splitting the current pick method
into two parts:
contains(event,picker) which returns truth value,details
pick(event) which generates the
On Fri, 06 Jul 2007 14:03:30 -0700, Christopher Barker wrote:
to, so maybe I'm missing something. In essence, I see a distinction
between contributing to a project someone else is releasing, and
creating a derived work that I release myself. Maybe there is no
difference.
I'll reply only to
There are two conspicuous bugs in the Cairo output:
1) contour_demo.py: the image part of the figure is wrong in shape and
content. It looks like an array dimensions confusion or something like
that. Strangely, the very similar image in image_demo.py is fine.
I fixed this bug. There
27 matches
Mail list logo
