Re: Dangerous update command

On 28 Nov, 20:23, Donald Arseneau <a...@xxxxxxxxx> wrote:
I don't think I understand why you need any kind of update there.
This is the very end of a fileevent handler. Simply returning will
cause Tcl to update and process the next event, whether a gui or a
file event. Is the problem that the gui events are queued up after
all the file events?


Yes, and it will just block all UI interactions while the file
transfer is progressing. So therefore a mechanism is needed to have
fileevents at "lower priority" than UI events. Using 'after idle' and
just schedule one fileevent at a time seems to be working well, but my
question was: is this the right way?

/Mats

.

Relevant Pages

  • htclient: new experimental HTTP Client
    ... Last week there was discussion of a problem with the http client which ... in the Tcl distribution. ... 50% of the time a [chan pending] after a fileevent returns ...
    (comp.lang.tcl)
  • Re: tcludp - bug when closing 1-of-2 listening ports
    ... fileevent handler blocks (since the "udp socket...closed" line doesn't ... My guess is, too, closing one port blocks/disables/removes the fileevent handler for the residual port, for whatever reason. ... BTW, the message "udp socket...closed" line did appear the first time close was called, and "AWAIT_EXIT=1" comes. ...
    (comp.lang.tcl)
  • Re: fileevent and vwait quiestion
    ... I have tested the procedure that call sendmesage in standalone mode ... when I run it from my C++ application that have Tcl embeded ... For examplie 'mime' package works fine. ... What can be the problem with fileevent and wait in my case? ...
    (comp.lang.tcl)
  • Re: Tcl, pipes and DJGPP
    ... Welcome on board Tcl. ... tempting to reply with a single URL to a manpage or wiki page: ... why a wiki page and not just "man fileevent"? ... some Windows programs work well as bidirectional pipes (plink is ...
    (comp.lang.tcl)
  • Re: POLL: Your favourite Tcl features
    ... Tcl's event loop was the first aspect ... Tcl, not being the best in interrupt-handling, ... consume&discard the line that triggered the fileevent, ... # show a prompt, and read commands: ...
    (comp.lang.tcl)