I have a solution that works.The problem is in 1/2 GTK and threads. unfortunetly threads are needed in this instance, idle timers [orig tried with them] have their issues which added their own problems, threads gave alot more benefits then they then problems they solved (I have a forum-thread on a
> "Jon" == Jon Roadley-Battin <[EMAIL PROTECTED]> writes:
Jon> is there any thread_init for matplotlib. short of having a
Jon> timer within the GUI class that checks if any new data is
Jon> present I cant see a way around this. It has to be done this
There isn't any such method. W
Message: 2Date: Mon, 04 Sep 2006 09:56:22 -0700From: Andrew Straw <
[EMAIL PROTECTED]>Subject: Re: [Matplotlib-users] matplotlib, GTK and ThreadsTo: Jon Roadley-Battin <[EMAIL PROTECTED]>,
matplotlib-users@lists.sourceforge.netMessage-ID: <[EMAIL PROTECTED]>Content-Type: text/plain; charset
Jon Roadley-Battin wrote:
> The problem I have with with the non-GUI thread calling the "plot"
> function.
That's your problem -- you should only call the GUI code (including
matplotlib, which eventually calls GTK) from a single thread. I suggest
looking at the Queue module to pass your data to th
I have run into a problem with matplotlib, GTK and Threading.The program basically gets data over RS232 and if a certain command is sent the data is plottedSo far the program is pretty mature and data can be read via RS232 and written to RS232 and the
GUI is updated (text-widgets) accordinglyThe p
