Wayne Watson wrote:
> The developer stated this in a msg this morning.
> Either way should work. Double clicking the py file is probably more
> convenient, but you can more easily see error messages if you open it
> with IDLE
option 3:
Start it up in a command window (DOS box on Windows), a
On 2/11/2010 11:42 AM, Wayne Watson wrote:
> That link has no reference to tkinter
http://matplotlib.sourceforge.net/examples/user_interfaces/embedding_in_tk.html
Read down a half dozen lines or so.
Alan Isaac
--
SOLAR
On 2/11/2010 11:36 AM, Wayne Watson wrote:
> you can more easily see error messages if you open it with IDLE
Why? Just call it from the command line
of a console window that you will leave open.
(Or write the error to file.)
Alan Isaac
-
Thanks. Got detoured by "not supported". I think I'll be printing our
your messages in the future. I just went back to one just now, and had
forgotten about your mentio of pyLab, model.
On 2/11/2010 7:38 AM, John Hunter wrote:
> On Thu, Feb 11, 2010 at 9:18 AM, Wayne Watson
> wrote:
>
>>
On Thu, Feb 11, 2010 at 10:42 AM, Wayne Watson
wrote:
> That link has no reference to tkinter. tk and tk2, plus a few others with
> tk in their names, but nothing else.A search in the box produced nothing.
As I said in my last email, the embedding_in_tk* files are the ones you want.
JDH
--
That link has no reference to tkinter. tk and tk2, plus a few others
with tk in their names, but nothing else.A search in the box produced
nothing.
On 2/11/2010 8:36 AM, Wayne Watson wrote:
Definitely tkinter. I'll look at the link. Interestingly though, and I
think I mentioned this. Ther
Definitely tkinter. I'll look at the link. Interestingly though, and I
think I mentioned this. There is another plot that's been working
fine. I seldom use it, but when I have, it seems to work.
The developer stated this in a msg this morning.
Either
way should work. Double clicking the py
On Thu, Feb 11, 2010 at 9:18 AM, Wayne Watson
wrote:
> Yes, certainly,as you explained a few days ago, the present use is
> incompatible with idle usage. Further, you mentioned the need for ipython
> and the "backend" to make it work (in IDLE?). The way we are using problem
> seems a bit ambiguou
On Thu, Feb 11, 2010 at 2:41 AM, Wayne Watson
wrote:
> A Ground Hog movie moment? Deja vu all over again (Quoting Yega Berra.).
>
> I went right through John Hunter's comment of a day or two ago about the
> need to solve this with ipython. That has to be taken into
> consideration; otherwise, this
A Ground Hog movie moment? Deja vu all over again (Quoting Yega Berra.).
I went right through John Hunter's comment of a day or two ago about the
need to solve this with ipython. That has to be taken into
consideration; otherwise, this is a no-go..
I suppose an interesting aside though on what
Foiled again. I clicked on the previous version, which has no MPL code
in the same def.
The show() is where things go wrong though. The question now is where
did the program go after the show()? Maybe it's time to put the
interactive debugger into play, which I've barely used. I have used others
11 matches
Mail list logo
