Hi everyone!
Is there any backend-independent way to get and set the figure window
coordinates and sizes (i.e. in pixels)? Currently when I make new plots they
appear in random locations as determined by my operating system; during
analysis when I'm making and destroying a lot of plot windows I wa
>
> I'm not sure what your intention is, but if you want to temporarily
> remove some artists from the axes, it would be easier to make them
> simply invisible. Otherwise, I recommend you to use the remove method.
>
> Regards,
>
> -JJ
>
>
>
> On Tue, Jul 1
Hello,
I'm writing a script that removes data from plots by looping over
axes.get_lines(), removing data, then using axes.set_lines(). It works quite
well, but when it's a plot with error bars, the vertical part of the error
bar is not disappearing.
I'm assuming the vertical part is a vline or som
rsday 21 August 2008 17:36:50 Eric Firing wrote:> Jack Sankey wrote:
>> > > pylab.gcf().clear(); pylab.show() # nothing happens
>> >
>> > With interactive mode off, in a script, show() should never be called
>> > more than once; it should be the last plot-rel
Thanks Eric,
I may be doing things a little bit weird since I've been with matplotlib for
many years. I did two things that fixed my problem: I wiped python25 out
completely and install enthought (with an older pylab). During the wipe I
noticed an extra pythonw running in the task manager that I h
I'm not sure if this is a matplotlib issue or what, but all of a sudden I
was not able to do gca() or gcf() correctly.
A simple command-line on pyshell (using wxAgg backend) went like this:
import pylab
pylab.plot([1,2,1]) # figure pops up
pylab.gca().clear(); pylab.show() # nothing happens
pylab
Hello again,
Just an update to the ginput() I'm using now. If you clicked really
fast using the previous version, the event queue would fill up and
you'd wind up getting extra clicks in your list. This version fixes
that and adds the ability to (a) terminate the collection process with
a right cli
round without a problem.
I suspect pylab.show() is responsible. It doesn't cause the whole
figure window to flicker when it updates, so I wager it's doing
something smarter than me. Consider me a convert. :)
Thanks!
-Jack
On Jan 18, 2008 9:28 AM, Jack Sankey <[EMAIL PROTECTED]&
Hey guys,
I'm not 100% sure if anyone has solved this problem, but I couldn't
find it, so here it is. This is based on a thread by Gael Varoquaux
about a year ago. The key element that was missing was the wx.Yield()
command, which gives up control of the current thread so the rest of
the world can
packages\matplotlib\backends\backend_agg.py",
line 301, in _get_agg_font
RuntimeError: Could not open facefile c:\windows\fonts\vera.ttf;
Cannot_Open_Resource
I'm pretty lost about it :)
Thanks,
Jack
On Jan 17, 2008 6:03 PM, Jack Sankey <[EMAIL PROTECTED]> wrote:
> Hello,
>
Hello,
I wrote a script that loops over some files, plotting them
individually with imshow(). In between each file, the program waits
for user input and then clears/closes the current figure before making
a new one.
Roughly 5-10 files into the loop, the script dies, outputting a loop
of stuff lik
Thanks guys! You can also just skip a step and go:
gca().fmt_xdata = str
gca().fmt_ydata = str
:)
I changed it in Axes.py. It would be cool if there was something in
matplotlibrc, but now that I understand how it works, it's no biggy to
me.
Take care,
Jack
On Jan 4, 2008 9:18 AM, John Hunter <
Hello,
When you make a figure and move the mouse around inside the axes, the
x- and y-values appear in the status bar. Is there a way to change the
precision of this data? It's only tracking 3 significant figures and I
need more (say you're zoomed in on some data with a large offset).
Is there a
Hello,
When I plot using the errorbar() routine, I get beautiful plots,
complete with error bars. Then, when I want to perform manipulations
on the data after the fact, I use
lines = axes.get_lines()
to get at the lines
lines[n].get_xdata() and set_xdata()
to edit the data etc...
The problem
14 matches
Mail list logo