matplotlib-users Mailing List for matplotlib

On 07/11/2010 07:52 AM, Preben Randhol wrote:

>>
>> Also, are you using backend_gtk or backend_gtkagg (and does it matter
>> for your problem?)
>
> I use GTKAgg and it works. GTK doesn't.
>

backend_gtk has limitations that backend_gtkagg does not, although I 
don't know that your zooming problem should be one of them.  Are you 
sure you *need* to use backend_gtk instead of backend_gtkagg?

Eric

Again, please post a complete free-standing example that replicates the 
problem, otherwise we can not help you. The binaries you are using are 
as close to any later official binaries as possible at this point and 
they pass all the example tests for the agg, cairo, and pdf backends.

Christoph


On 7/11/2010 12:12 PM, Ademir Francisco da Silva wrote:
>    Em 11/07/2010 13:56, John Hunter escreveu:
>> On Sun, Jul 11, 2010 at 11:15 AM, Ademir Francisco da Silva
>>> Case closed. Finally I find it..., but for my success I have taken off the
>>> #  of the  #interactive  : False  on the line #37 from this file
>>> matplotlib\\mpl-data\\matplotlibrc  and everything works fine now.
>> I don't think this flag will affect whether or nor widgets is
>> imported.  Are you sure you haven't made some other changes?
>>
>>> But I have another important question for all of you..., recently I have
>>> changed my Python's version from 2.6.5 to 2.7 and since I did it my
>>> widgets.Cursor and widgets.Button do not work, so anyone have a idea about
>>> this behavior to tell me, please ???
>>>
>>> Further information ...
>>> My code is the same and before it works fine but now it just not works ...,
>>> just take a look in the excerpt of my code below ...
>>>
>>> widgets.Cursor( axe, useblit = True, color = self.cor[ 477 ][ 1 ], lw = 2 )
>>> widgets.Button( pyplot.axes( [ .91, .1, .08, .06 ] ), self.textName[ 19 ],
>>>                          color = self.cor[ 403 ][ 1 ], hovercolor = self.cor[
>>> 46 ][ 1 ] ).\
>>>                          on_clicked( self.button_12Click )
>>>
>>> How may I fix it, please ???
>> Did you compile matplotlib for python2.7 yourself -- we haven't
>> released any binaries yet for that version.  Can you paste a complete
>> free-standing example that replicates the problem as wee as the output
>> of your script on your system when you pass in the --verbose-helpful
>> flag?
>>
>> JDH
>>
>>
> Hi John ...,
>
> I am just take that binarie from this internet address
> http://www.lfd.uci.edu/~gohlke/pythonlibs/
> Hmmmm..., so I was wondering that the problem is it and I will have to
> wait for the official version of the matplotlib binaries for the Python
> 2.7( win64 ). Sucks...!
> I hope to have that binaries asap and after the installation of it I
> will verify if that problem continues.
>
> anyway I really enjoyed your prompt aid ..., Thanks.
>
>
> Cheers,
>
>
> --
> Ademir Francisco da Silva
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

  Em 11/07/2010 13:56, John Hunter escreveu:
> On Sun, Jul 11, 2010 at 11:15 AM, Ademir Francisco da Silva
>> Case closed. Finally I find it..., but for my success I have taken off the
>> #  of the  #interactive  : False  on the line #37 from this file
>> matplotlib\\mpl-data\\matplotlibrc  and everything works fine now.
> I don't think this flag will affect whether or nor widgets is
> imported.  Are you sure you haven't made some other changes?
>
>> But I have another important question for all of you..., recently I have
>> changed my Python's version from 2.6.5 to 2.7 and since I did it my
>> widgets.Cursor and widgets.Button do not work, so anyone have a idea about
>> this behavior to tell me, please ???
>>
>> Further information ...
>> My code is the same and before it works fine but now it just not works ...,
>> just take a look in the excerpt of my code below ...
>>
>> widgets.Cursor( axe, useblit = True, color = self.cor[ 477 ][ 1 ], lw = 2 )
>> widgets.Button( pyplot.axes( [ .91, .1, .08, .06 ] ), self.textName[ 19 ],
>>                          color = self.cor[ 403 ][ 1 ], hovercolor = self.cor[
>> 46 ][ 1 ] ).\
>>                          on_clicked( self.button_12Click )
>>
>> How may I fix it, please ???
> Did you compile matplotlib for python2.7 yourself -- we haven't
> released any binaries yet for that version.  Can you paste a complete
> free-standing example that replicates the problem as wee as the output
> of your script on your system when you pass in the --verbose-helpful
> flag?
>
> JDH
>
>
Hi John ...,

I am just take that binarie from this internet address    
http://www.lfd.uci.edu/~gohlke/pythonlibs/
Hmmmm..., so I was wondering that the problem is it and I will have to 
wait for the official version of the matplotlib binaries for the Python 
2.7( win64 ). Sucks...!
I hope to have that binaries asap and after the installation of it I 
will verify if that problem continues.

anyway I really enjoyed your prompt aid ..., Thanks.


Cheers,


-- 
Ademir Francisco da Silva

On Fri, 9 Jul 2010 19:37:56 -0500
John Hunter <jd...@gm...> wrote:

> On Fri, Jul 9, 2010 at 3:10 PM, Preben Randhol <ra...@pv...>
> wrote:
> 
> > I'm trying to plot several subplots. I have setup a scrollwidget and
> > viewport and I pack a canvas into a vbox in the viewport.
> >
> > Problem is that when I scroll, either some of the subplots are
> > missing, or I get an error when I try to zoom on a graph that
> > argument is not a gdk.gtk.image (or something like that) but None.
> >
> > I thought this was fixed in 1.0, but it isn't
> >
> > Please advice!
> 
> Does this example work for you?
> 
>   http://matplotlib.sourceforge.net/examples/user_interfaces/embedding_in_gtk3.html


Yes it works and a bit cleanup of my imports helped in my program too.
However if I add NavigateToolbar to the example above I get problems.

mtoolbar = NavigationToolbar(canvas, win)

then I get error when I try to zoom in a graph:

/usr/lib/pymodules/python2.6/matplotlib/backends/backend_gtk.py:621:
DeprecationWarning: Use the new widget gtk.Tooltip self.tooltips =
gtk.Tooltips() /usr/lib/pymodules/python2.6/matplotlib/backends/backend_gtk.py:601:
GtkWarning: gdk_drawable_copy_to_image: assertion `src_y >= 0' failed
self._imageBack = axrect, drawable.get_image(*axrect) Traceback (most
recent call last): File
"/usr/lib/pymodules/python2.6/matplotlib/backends/backend_gtk.py", line
606, in idle_draw drawable.draw_image(gc, imageBack, 0, 0, *lastrect)
TypeError: Gdk.Drawable.draw_image() argument 2 must be gtk.gdk.Image,
not None

The graph zooms, but I don't see the rubberband. I got same
error in 1.0:
 
TypeError: Gdk.Drawable.draw_image() argument 2 must be gtk.gdk.Image,
not None


> It uses a ScrolledWindow.
> 
> Also, are you using backend_gtk or backend_gtkagg (and does it matter
> for your problem?)

I use GTKAgg and it works. GTK doesn't.

> 
> If you could create a minimal example starting with
> embedding_in_gtk3.py that replicates your problem, we're more likely
> to be able to help.

I have added the example above with my changes. Zooming is the problem.

On Sun, Jul 11, 2010 at 11:15 AM, Ademir Francisco da Silva
> Case closed. Finally I find it..., but for my success I have taken off the
> #  of the  #interactive  : False  on the line #37 from this file
> matplotlib\\mpl-data\\matplotlibrc  and everything works fine now.

I don't think this flag will affect whether or nor widgets is
imported.  Are you sure you haven't made some other changes?

> But I have another important question for all of you..., recently I have
> changed my Python's version from 2.6.5 to 2.7 and since I did it my
> widgets.Cursor and widgets.Button do not work, so anyone have a idea about
> this behavior to tell me, please ???
>
> Further information ...
> My code is the same and before it works fine but now it just not works ...,
> just take a look in the excerpt of my code below ...
>
> widgets.Cursor( axe, useblit = True, color = self.cor[ 477 ][ 1 ], lw = 2 )
> widgets.Button( pyplot.axes( [ .91, .1, .08, .06 ] ), self.textName[ 19 ],
>                         color = self.cor[ 403 ][ 1 ], hovercolor = self.cor[
> 46 ][ 1 ] ).\
>                         on_clicked( self.button_12Click )
>
> How may I fix it, please ???

Did you compile matplotlib for python2.7 yourself -- we haven't
released any binaries yet for that version.  Can you paste a complete
free-standing example that replicates the problem as wee as the output
of your script on your system when you pass in the --verbose-helpful
flag?

JDH

  Em 11/07/2010 12:22, Ademir Francisco da Silva escreveu:
> Hi all ...,
>
> Anyone may tell me what happend with the /widgets/  in the matplotlib???
>
> Before it is here ...,  from matplotlib import widgets
>
> but now it is vanished ..., or where it is ???
>
> Further informations ...
> my matplotlib version is 1.0.0 - $Revision: 8503 $
> my numpy version is 1.5.0.dev8469
> my OS is Windows Vista 64
>
> Thank you very much for any help.
>
> Cheers,
>
>
> -- 
> Ademir Francisco da Silva
Hello again ...,

Case closed. Finally I find it..., but for my success I have taken off 
the  #  of the  #interactive  : False  on the line #37 from this file  
matplotlib\\mpl-data\\matplotlibrc  and everything works fine now.

But I have another important question for all of you..., recently I have 
changed my Python's version from 2.6.5 to 2.7 and since I did it my  
widgets.Cursor and widgets.Button do not work, so anyone have a idea 
about this behavior to tell me, please ???

Further information ...
My code is the same and before it works fine but now it just not works 
..., just take a look in the excerpt of my code below ...

widgets.Cursor( axe, useblit = True, color = self.cor[ 477 ][ 1 ], lw = 2 )
widgets.Button( pyplot.axes( [ .91, .1, .08, .06 ] ), self.textName[ 19 ],
                         color = self.cor[ 403 ][ 1 ], hovercolor = 
self.cor[ 46 ][ 1 ] ).\
                         on_clicked( self.button_12Click )

How may I fix it, please ???


Cheers,


-- 
Ademir Francisco da Silva

  Hi all ...,

Anyone may tell me what happend with the /widgets/  in the matplotlib???

Before it is here ...,  from matplotlib import widgets

but now it is vanished ..., or where it is ???

Further informations ...
my matplotlib version is 1.0.0 - $Revision: 8503 $
my numpy version is 1.5.0.dev8469
my OS is Windows Vista 64

Thank you very much for any help.

Cheers,


-- 
Ademir Francisco da Silva

>>Any chance you can test this with the latest release 1.0.0?
>>JDH

Tried 1.0.0 but first I should explain what I want more clearly in case I am
missing something.
I want to run a long calculation and have some early results plotted (and
become visible) without needing to close the window as the show() command
now requires.  I am happy to run in ipython -pylab to achieve this, and
recognise that the plots might/will be delayed if I use ipython (no pylab)
or straight python. 

I also would like the control to suppress the interactive rendering for some
plots, such as those that overlay many curves.  When all the curves have
been added to the object (typically by plot()), then I would like them
rendered - this is faster than re-rendering every time a curve is added.

I was able to achieve this with ion(), isinteractive(), and show() in
previous versions.

How should I do it now (especially as show() is now(1.0.0) supposed to
block?

======  Back to your suggestion =======
OK, after aptitude install python-dev tk8.5-dev tcl8.5-dev python-gtk2-dev
1.0.0 can be built

It passes the simple test in the initial post, (good), but is still delayed
in real code - i.e. in script or compiled code.

In the interests of simplicity, I had reduced my test case to the absolute
simplest, equivalent to typing at the command prompt.

Below are two better examples: the first is still very brief, but better
represents real code, and works on ubuntu9.04 and Enthought for w7.  
Following is a longer example which is also simplified.  I left a few extra
lines commented out to show you what I have tried.

After the code snippets is a list of what versions do and do not work
interactively (as described above).

=======short_test.py==
# graph should appear immediately, the update after 3 secs, prompt at 6 secs
import pylab as pl
import time

def test():
    pl.plot([1,2])
    pl.show()
    time.sleep(3)

print(pl.isinteractive())
pl.ion()
pl.plot([3,4])
pl.show()
time.sleep(3)
test()


==========interactive_plot_test.py===========
""" Test the ability of plots to be interactive - in the sense that
they display as they go, rather than waiting til the command prompt is
reached.
These might well be on different figures, or subplots but I kept it simple.
"""
import pylab as pl
import time

def int_plot():
    print('plot intermediate result')
#    pl.figure()
    pl.plot([2,1])
    pl.title('intermediate result')
    
#    pl.draw_if_interactive()
#    pl.show()                  #?? (mainloop=False)
    time.sleep(3)

print('When run, the plot should appear immediately, '
      ' then the prompt after sleep(2)')
print('test on "scripted" code - ipython may treat differently')
pl.ion()
pl.plot([3,4], hold=0)
#pl.show()
time.sleep(3)
print('same test on compiled code')
int_plot()

=========================

List of what works (and not):

works under ubuntu 9.04 dist (tested under w32 VMPlayer)
Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41) 
IPython 0.9.1 matplotlib '0.98.5.2'  tkagg backend

works under Win7 Enthought
Python 2.6.4 |EPD 6.1-1 (32-bit)| (r264:75706, Nov 11 2009, 19:42:36) [MSC
v.150
0 32 bit (Intel)]
IPython 0.10  matplotlib: '0.99.1.1' backend_wx.py

*not* under ubuntu 10.04/2.6.5/0.10 with matplotlib 1.0.0 compiled as above
WXAgg:   nothing appears until 6 sec, prompt is blocked
TkAgg:   nothing appears until 6 sec, prompt is not blocked
GTKAgg:  nothing appears until 6 sec, prompt is not blocked


John Hunter-4 wrote:
> 
> On Fri, Jul 9, 2010 at 9:52 PM, bdb112 <boy...@an...> wrote:
> 
>> print('When pasted in to ipython -pylab, the plot should appear
>> immediately,
>> '
>>      ' then the ipython prompt after sleep(2): but the plot waits until
>> the
>> prompt!')
>> plot([3,4], hold=0)
>> ion()
>> show()
>> time.sleep(2)
>>
>> Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
>> IPython 0.10
>> matplotlib.__version__   Out[3]: '0.99.1.1
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 

-- 
View this message in context: http://old.nabble.com/interactive-plots-in-ipython--pylab-are-delayed-until-ipython-prompt-tp29123816p29129079.html
Sent from the matplotlib - users mailing list archive at Nabble.com.