Tuvas,
I fully agree with Eric's post above. You may additionnaly have to kill
the main window before exit, to avoid a nasty thread related error
message and occasionally some zombie procs:
import Tkinter,atexit
top=Tkinter.Tk()
.../...
atexit.register(lambda top=top: top.destroy())
top.mainloop(
On 24 Jan 2006 12:37:01 -0800, Tuvas <[EMAIL PROTECTED]> wrote:
> I thought I mentioned that I'm running in linux, and yes, there are
> threads involved. I just don't know why on one machine that it would
> run so differently than another.
The only secure way I found to make Tkinter mix with threa
I thought I mentioned that I'm running in linux, and yes, there are
threads involved. I just don't know why on one machine that it would
run so differently than another.
As to re-writing my whole code, well, I've got around 2500 lines of
code, and while re-writing would be faster I'm sure, I still
On 23 Jan 2006 11:28:37 -0800, Tuvas <[EMAIL PROTECTED]> wrote:
> I am building a tkinter program. A part of this program is to read data
> from an incoming interface, and depending on the data, will display a
> bit of text on the tk dialog, it decodes this data, so to speak. If one
> command is s
Tuvas wrote:
> Only 1 process initiated Tkinter.Tk. I guess this'll just be a tough
> bug hunt... It drives me nuts that it should work, it just doesn't for
> some reason... I guess I can try various things to make it work, but,
> well, I would rather that it just works to start out with...
>
If
Only 1 process initiated Tkinter.Tk. I guess this'll just be a tough
bug hunt... It drives me nuts that it should work, it just doesn't for
some reason... I guess I can try various things to make it work, but,
well, I would rather that it just works to start out with...
--
http://mail.python.org/
Tuvas wrote:
> Nope, that's the oddest thing about it all... Perhaps the statement is
> called twice or something along those lines, but there again, I can't
> see how it would be...
>
Very strange behavior can occur if the same python process instantiates
Tkinter.Tk more than once (either con
Nope, that's the oddest thing about it all... Perhaps the statement is
called twice or something along those lines, but there again, I can't
see how it would be...
--
http://mail.python.org/mailman/listinfo/python-list
Tuvas wrote:
> I am building a tkinter program. A part of this program is to read data
> from an incoming interface, and depending on the data, will display a
> bit of text on the tk dialog, it decodes this data, so to speak. If one
> command is sent, everything's just fine. When multiple are sent,
