matplotlib-users Mailing List for matplotlib

On Mar 10, 2006, at 2:01 PM, Onsi Fakhouri wrote:
> Ken, if you want me to try something let me know -- my guess is I'm 
> using a different version of either the AGG library or wx.
I'm afraid that I'm at a loss right now. Knowing exactly what 
version of MacOS, Python, wxPython, and matplotlib you're using might 
help.
If you have MacOS 10.4, Python 2.3, and wxPython 2.6.2.1, then you 
could see if you have the same problem with my build of matplotlib:
	http://agni.phys.iit.edu/~kmcivor/downloads/matplotlib-0.87.1-py2.3- 
macosx-10.4-ppc.egg
> As an aside, does the cpp implementation run much faster than the 
> python implementation?
You probably won't notice a difference unless you're doing 
animations. If you are, then it provides a big speedup under Linux 
but much less of a speedup on a Mac. I think the difference is due 
to the way wxWidgets is implemented on the two platforms.
Ken

On Mar 10, 2006, at 2:56 PM, Christopher Barker wrote:
> This might have something to do with the fact that OS-X double 
> buffers it's windows, so you need to force and update event 
> somehow. A call to wx.Window.Refresh() and/or wx.Window.Update() 
> might do it.
For `examples/anim.py', calling line.axes.figure.canvas.Update() 
after each call to pylab.draw() appears to do the trick.
> Maybe OS-X waits for a Idle event to update the screen.
The wxWidgets documentation for wxWindow::Refresh() and 
wxWindow::Update() indicates that the event loop is the default 
method for driving screen repaints.
> What kind of app would you have running without an event loop anyway?
Apparently, pylab scripts that try to animate plots by redrawing them 
run without an event loop. I could be mistaken, but I don't think 
the loop is started until you call pylab.show(). See `examples/ 
anim.py' for an example of what I'm talking about.
> Id didn't think you could do much at all without one in wx.
I didn't think so either but I hadn't considered pylab. Since a 
matplotlib example was the initial source of the problem, I think we 
should probably change things so that Update() gets called when 
necessary. My proposal is to tack the following (untested) lines to 
the end of backend_wx.FigureCanvasWx.gui_repaint():
	# force a repaint if we think we're a pylab figure
	if isinstance(self.GetParent(), FigureFrameWx):
		self.Update()
Ken

Chris Seberino wrote:
> I made my plot PNGs transparent. For some reason this works
> in Firefox but not in Internet Explorer.
> 
> Anyone know why?
There is a known problem with transparent PNGs in IE, one of the reasons 
that they haven't become as popular as you might have expected/hoped.
This article gives some background, although this was just one search 
result I found :)
 http://www.pcmag.com/article2/0,1759,1645331,00.asp
According to the article the problem appears where the palette size is 
not 256. Perhaps there is a workaround which could be used in the png 
output code? Or perhaps 256 colours is often not suitable - eg. 
antialiasing is used in output (requiring more colours)?
-- 
Neil

Robert Hetland wrote:
> Indeed, I did not know about it.
> 
> When I checked a while back, I did not notice any universal builds.
It's very new, but has gotten a lot of discussion on the python-mac 
list. That's a very good list to subscribe to if your using Python on a 
Macintosh.
> am pretty happy with my home rolled build. Are there any special 
> reasons to put python in the /Library/Frameworks directory? I imagine
> there are, and I'm just not clued in enough to know why..
Honestly, I'm not that clued in to what exactly the advantage is a 
framework -- but I do know it's more than just where it happens to live.
One advantage to the framework build is that you can use py2App to make 
a .app bundle of your program -- I don't know if it works with a 
standard unix-style build.
By the way, you can build it yourself as a Framework with a flag like 
--enable-framework or something like that.
The current goal of the macpython crowd is to establish a more or less 
"standard" build -- the universal framework build, and then we can 
populate pythonmac.org with pre-build extension packages for it.
This will be a big help to folks (unlike yourself) that wouldn't dream 
of building python from source.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

On Mar 10, 2006, at 3:00 PM, Christopher Barker wrote:
> Or did you not know about it?
Indeed, I did not know about it.
When I checked a while back, I did not notice any universal builds. 
I am pretty happy with my home rolled build. Are there any special 
reasons to put python in the /Library/Frameworks directory? I 
imagine there are, and I'm just not clued in enough to know why..
Thanks for the tip,
-Rob.
-----
Rob Hetland, Assistant Professor
Dept of Oceanography, Texas A&M University
p: 979-458-0096, f: 979-845-6331
e: he...@ta..., w: http://pong.tamu.edu