On Mon, Nov 9, 2009 at 3:55 PM, Andrew Straw wrote:
> What's the motivation of the ps backend "compositing" (rasterizing to a
> single bitmap) multiple images? It seems it will, by design, preclude the
> use of non-image artists between two images. I guess the motivation is to
> reduce output file
On Mon, Nov 9, 2009 at 3:08 PM, Leonid Petrov wrote:
> Hi, John,
>
> I got mpl from
>
> http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.1/matplotlib-0.99.1.1.tar.gz/download
>
> /d1/incoming> md5sum matplotlib-0.99.1.1.tar.gz
> bd0894dd924eb5bec84c42d26041a544 matplot
Hi, John,
I got mpl from
http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.1/matplotlib-0.99.1.1.tar.gz/download
/d1/incoming> md5sum matplotlib-0.99.1.1.tar.gz
bd0894dd924eb5bec84c42d26041a544 matplotlib-0.99.1.1.tar.gz
I removed source code of matplotlib-0.99.1.1
Jae-Joon Lee wrote:
> On Mon, Nov 9, 2009 at 12:44 PM, Eric Firing wrote:
>
>> PS backend already does things differently from others because it doesn't
>> handle alpha, correct? Does the patch make this situation any worse?
>>
>>
>
> When there are multiple Images and render.option_image
Darren,
Have you happened to review Pierre's patch for the toolbar
improvement? I am interested to see this integrated in mpl soon.
Thanks.
On Mon, Nov 9, 2009 at 2:43 PM, Pierre Raybaut wrote:
> Hi,
>
> I've already sent everything to Darren. I don't have any news but I
> guess that it will be
On Mon, Nov 9, 2009 at 1:29 PM, Leonid Petrov wrote:
> Hi, matplotlibers,
>
> I tried to compile matplotlib0.99.1.1 against Python-2.6.4, numpy-1.3.0,
> libpng-1.2.40, freetype-2.3.11 with the following command:
> python setup.py install --prefix=/opt64 > & comp.log
>
> I got
>
> building 'matpl
Hi, matplotlibers,
I tried to compile matplotlib0.99.1.1 against Python-2.6.4, numpy-1.3.0,
libpng-1.2.40, freetype-2.3.11 with the following command:
python setup.py install --prefix=/opt64 > & comp.log
I got
building 'matplotlib.backends._macosx' extension
/opt64/bin/gcc -fno-strict-alias
On Mon, Nov 9, 2009 at 12:44 PM, Eric Firing wrote:
> PS backend already does things differently from others because it doesn't
> handle alpha, correct? Does the patch make this situation any worse?
>
When there are multiple Images and render.option_image_nocomposite()
is false (as in the ps bac
On Mon, Nov 9, 2009 at 12:16 PM, Andrew Straw wrote:
> So now the question for me is what is this option_image_nocomposite is so
> that I can generalize the patch to both when it's True and False. From the
The compositing is in support of things like
pylab_examples/layer_images.py, where two ima
On Mon, Nov 9, 2009 at 12:12 PM, Jae-Joon Lee wrote:
> On Mon, Nov 9, 2009 at 1:01 PM, John Hunter wrote:
>> Your
>> patch is only applied when len(images)<=1 or
>> renderer.option_image_nocomposite(), both of which will be False when
>> using Agg with multiple images, no?
>
> I believe renderer.
John Hunter wrote:
> On Mon, Nov 9, 2009 at 10:21 AM, Andrew Straw wrote:
>
>> Hi All,
>>
>> I have addressed what I think is a long-standing wart: zorder is mostly
>> ignored for imshow(). (See e.g.
>> http://old.nabble.com/Re%3A--Matplotlib-users--imshow-zorder-tt19047314.html#a19047314
>> )
On Mon, Nov 9, 2009 at 1:01 PM, John Hunter wrote:
> Your
> patch is only applied when len(images)<=1 or
> renderer.option_image_nocomposite(), both of which will be False when
> using Agg with multiple images, no?
I believe renderer.option_image_nocomposite() is True for the agg backend.
So, it
On Mon, Nov 9, 2009 at 10:21 AM, Andrew Straw wrote:
> Hi All,
>
> I have addressed what I think is a long-standing wart: zorder is mostly
> ignored for imshow(). (See e.g.
> http://old.nabble.com/Re%3A--Matplotlib-users--imshow-zorder-tt19047314.html#a19047314
> ) The question is whether I should
Jae-Joon Lee wrote:
> Andrew,
>
> One of my worry is that this can results in inconsistent ouputs
> between backends. Your patch only affects backends with compositing
> capabilities. And backends such as ps backend will still render images
> at the bottom of all other artists.
PS backend already
Andrew,
One of my worry is that this can results in inconsistent ouputs
between backends. Your patch only affects backends with compositing
capabilities. And backends such as ps backend will still render images
at the bottom of all other artists.
I think it is often sufficient if we draw images a
Andrew Straw wrote:
> Hi All,
>
> I have addressed what I think is a long-standing wart: zorder is mostly
> ignored for imshow(). (See e.g.
> http://old.nabble.com/Re%3A--Matplotlib-users--imshow-zorder-tt19047314.html#a19047314
>
> ) The question is whether I should apply the attached patch.
On Mon, Nov 09, 2009 at 08:21:30AM -0800, Andrew Straw wrote:
> Hi All,
>
> I have addressed what I think is a long-standing wart: zorder is mostly
> ignored for imshow(). (See e.g.
> http://old.nabble.com/Re%3A--Matplotlib-users--imshow-zorder-tt19047314.html#a19047314
>
> ) The question is
Hi All,
I have addressed what I think is a long-standing wart: zorder is mostly
ignored for imshow(). (See e.g.
http://old.nabble.com/Re%3A--Matplotlib-users--imshow-zorder-tt19047314.html#a19047314
) The question is whether I should apply the attached patch.
The worry is that someone is rel
You are right. The error disappeared after re-building the matploblib.
Thanks for pointing out this.
On Mon, Nov 9, 2009 at 8:41 AM, Michael Droettboom wrote:
> I can't reproduce this here. These sorts of CXX errors are usually caused
> by distutils not rebuilding enough when things change.
I can't reproduce this here. These sorts of CXX errors are usually
caused by distutils not rebuilding enough when things change. Can you
try removing the build directory, rebuilding matplotlib, and then
rebuilding the docs?
Mike
On 11/07/2009 12:10 PM, Gökhan Sever wrote:
Hello,
The lates
20 matches
Mail list logo
