Strange Tkinter behaviour

[Michael Hudson]

"Tomasz Lisowski" <jtlispl at poczta.NOSPAM.onet.pl> writes:

> Uzytkownik "Michael Hudson" <mwh at python.net> napisal w wiadomosci
> news:ulmgpr2i9.fsf at python.net...
> > "Tomasz Lisowski" <jtlispl at poczta.NOSPAM.onet.pl> writes:
> >
> > > I wonder, whether there is a mechanism suspending the Tkinter event
> > > loop, so that other event-based applications (not using Tkinter)
> > > could get access, and perform their duties.
> >
> > Unix or Windows?
> 
> Windows

Ah.  Can't help you then.

> >
> > Have you looked at createfilehandler?
> 
> ??? What for? This does not seem to concern 'files'.

No, but createfilehandler lets you do things when things turn up on
file descriptors, which on Unix lets you allow for situations where:

> > > other event-based applications (not using Tkinter) could get
> > > access, and perform their duties.

> > What are you trying to do again?  I think I've got a bit confused...
> 
> Please read my original post. Nevertheless ...

I did, and was still confused.  Sorry.

> I am trying to make the text drawing routine (from the native CAD system
> producer's module) to show the text immediately, as it used to do, when
> Tkinter was not used.
> 
> If I am using Tkinter, and the root window is functionning, the text id
> displayed only if the button adding the text is clicked again.

Oh.  Then I think I got this confused with another thread.  Sorry for
the confusion.

Cheers,
M.

-- 
  I also feel it essential to note, [...], that Description Logics,
  non-Monotonic Logics, Default Logics and Circumscription Logics 
  can all collectively go suck a cow. Thank you.
              -- http://advogato.org/person/Johnath/diary.html?start=4