Hi Jae-Loon,
thanks for your comments! Of course I do agree that a figure layout
should not change in interactive mode. However, I don't see why this
should happen upon a panning action. A different case is when the
label or title font sizes are changed, but I was assuming this is
adjusted prior
On Wed, May 11, 2011 at 5:03 PM, Daniel Mader
danielstefanma...@googlemail.com wrote:
Hi Jae-Loon,
thanks for your comments! Of course I do agree that a figure layout
should not change in interactive mode. However, I don't see why this
should happen upon a panning action. A different case is
Hi again,
Hi Jae-Loon,
thanks for your comments! Of course I do agree that a figure layout
should not change in interactive mode. However, I don't see why this
should happen upon a panning action. A different case is when the
label or title font sizes are changed, but I was assuming this is
Hi,
we're running Matplotlib 1.0.0 with Python 2.6.2 on CentOS 5.6. When
importing from matplotlib._path, users get an error message
undefined symbol:
_ZSt16__ostream_insertIcSt11char_traitsIcEERSt13basic_ostreamIT_T0_ES6_PKS3_l
I'm at a loss. There were no errors during the installation
On Wed, May 11, 2011 at 11:07 AM, C M cmpyt...@gmail.com wrote:
On Wed, May 11, 2011 at 12:29 AM, Jae-Joon Lee lee.j.j...@gmail.com wrote:
I think I fixed a similar bug at some point but I'm not sure if that
is related with this.
Are you using the *make_axes_area_auto_adjustable* from the
[Accidentally sent this reply privately the first time, natch.]
On 2011-05-11 04:29, Jae-Joon Lee wrote:
On Wed, May 11, 2011 at 5:03 PM, Daniel Mader
danielstefanma...@googlemail.com wrote:
Hi Jae-Loon,
thanks for your comments! Of course I do agree that a figure
layout
On Wed, May 11, 2011 at 12:47 PM, Brendan Barnwell brenb...@brenbarn.netwrote:
[Accidentally sent this reply privately the first time, natch.]
On 2011-05-11 04:29, Jae-Joon Lee wrote:
On Wed, May 11, 2011 at 5:03 PM, Daniel Mader
danielstefanma...@googlemail.com wrote:
Hi
On Wed, May 11, 2011 at 1:59 PM, Benjamin Root ben.r...@ou.edu wrote:
...
Most things, we do know the sizes of. It is my understanding that it is
the text objects that is the unknown. If this could be solved, then a
layout engine would be much more feasible. The problem is that even LaTeX
On Wed, May 11, 2011 at 1:59 PM, Benjamin Root ben.r...@ou.edu wrote:
On Wed, May 11, 2011 at 12:47 PM, Brendan Barnwell brenb...@brenbarn.net
wrote:
One thing I've always wondered: is it fundamentally impossible to
change the fact that, in matplotlib, you cannot know how big a drawn
On Wed, May 11, 2011 at 1:43 PM, todd rme toddrme2...@gmail.com wrote:
On Wed, May 11, 2011 at 1:59 PM, Benjamin Root ben.r...@ou.edu wrote:
On Wed, May 11, 2011 at 12:47 PM, Brendan Barnwell
brenb...@brenbarn.net
wrote:
One thing I've always wondered: is it fundamentally
On 05/11/2011 09:11 AM, Benjamin Root wrote:
On Wed, May 11, 2011 at 1:43 PM, todd rme toddrme2...@gmail.com
mailto:toddrme2...@gmail.com wrote:
On Wed, May 11, 2011 at 1:59 PM, Benjamin Root ben.r...@ou.edu
mailto:ben.r...@ou.edu wrote:
On Wed, May 11, 2011 at
On Wed, May 11, 2011 at 4:31 PM, Eric Firing efir...@hawaii.edu wrote:
On 05/11/2011 09:11 AM, Benjamin Root wrote:
On Wed, May 11, 2011 at 1:43 PM, todd rme toddrme2...@gmail.com
mailto:toddrme2...@gmail.com wrote:
On Wed, May 11, 2011 at 1:59 PM, Benjamin Root ben.r...@ou.edu
Hi,
I've come across something I don't entirely understand in the
behaviour of gridspec. It's not obvious from the code docs for this
module, but is it only supposed to be able to deal with 'square'
layouts, e.g. 3x3, 4x4 etc?
Taking some code from an example on the gridspec page ...
import
2011/5/12 David Andrews irbda...@gmail.com:
Hi,
I've come across something I don't entirely understand in the
behaviour of gridspec. It's not obvious from the code docs for this
module, but is it only supposed to be able to deal with 'square'
layouts, e.g. 3x3, 4x4 etc?
Taking some code
On Thu, May 12, 2011 at 2:37 AM, Brendan Barnwell brenb...@brenbarn.net wrote:
One thing I've always wondered: is it fundamentally impossible to change the
fact that, in matplotlib, you cannot know how big a drawn object will be
until you actually draw it?
Well, I don't think this is 100%
On Thu, May 12, 2011 at 2:59 AM, Benjamin Root ben.r...@ou.edu wrote:
Most things, we do know the sizes of. It is my understanding that it is the
text objects that is the unknown. If this could be solved, then a layout
engine would be much more feasible.
I doubt it. As far as I know, the
Yes, this is a bug that has been fixed.
https://github.com/matplotlib/matplotlib/commit/76851eb
Regards,
-JJ
On Thu, May 12, 2011 at 7:53 AM, Goyo goyod...@gmail.com wrote:
2011/5/12 David Andrews irbda...@gmail.com:
Hi,
I've come across something I don't entirely understand in the
On Thu, May 12, 2011 at 7:18 AM, David Andrews irbda...@gmail.com wrote:
I'm quite interested in getting involved with mpl development, partly
as a way to get my head around python numpy and aid porting a bunch
of stuff I use over to python from IDL. Unless I'm doing something
totally wrong
18 matches
Mail list logo
