I'm using homebrew python, which is built from source, and the latest
matplotlib gotten from git://github.com/matplotlib/matplotlib.git. (I
rebuilt it ~2 minutes ago)
Perhaps there's some kind of environment difference?
-E
On Wed, Apr 11, 2012 at 5:12 AM, Zachary Pincus <zachary.pin...@yale.edu>wrote:
> > 1. Keyboard input always goes to the terminal. Shortcuts don't work in
> the standard plot windows and my custom widgets no longer catch
> key_press_events (I'm not sure when this functionality broke exactly as I
> haven't used those widgets much recently but it worked when I developed 'em
> a year or two ago.)
> >
> > 2. There's no icon in the cmd-tab task switcher corresponding to the
> figure windows. Swapping to the terminal running ipython (or the qtconsole
> for ipython qtconsole) does not raise the windows.
> >
> > 3. Using mission control, the figures appear grouped as if they belong
> to an application of their own. However, when you click on them to swap to
> them and bring them forward from behind other windows, they raise and then
> immediately disappear again. I think that mission control is raising the
> specific window you select from the collection of figures, but then OSX is
> somehow immediately re-raising the previously selected app, which hides the
> figures again.
>
> Hmm, I don't really see these issues, using a dev matplotlib, OS X 10.7.3,
> and a python.org python 2.7. Interesting. (This is with the 'MacOSX'
> backend, mind. Also note that on March 5 there was a patch to that backend
> to fix a few issues, so if your matplotlib checkout is before that, perhaps
> that's the problem?)
>
> Anyhow, when I start python (or ipython), and then do "import
> matplotlib.pyplot as plt", nothing happens, but then "plt.figure()", for
> example, causes a new dock icon to appear -- a python rocket-ship thing --
> that acts as an "app" that owns the figure windows. I can use this app to
> switch to / raise the windows from the dock or the cmd-tab switcher, and
> things work correctly via mission control as well.
>
> The keyboard shortcuts are a bit flaky ('s' never seems to work, but I can
> e.g. toggle gridlines with 'g' or log-axes with 'l'), but the key-presses
> definitely don't go to the terminal.
>
> I wonder what the difference is? Perhaps the apple-supplied python is a
> bit broken in this regard?
>
> Zach
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Matplotlib-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
