Re^2: Tk fileevent 'readable' stops working

But the same algorithm using Event::Lib or plain select() works perfectly (tested), so what's wrong with Tk's event loop?

BTW, people are using computers for such "too difficult for people" tasks. And i don't see any problem in sending and receiving data at the same time on full duplex channel, that tcp connection claims to be.

Comment on Re^2: Tk fileevent 'readable' stops working

Replies are listed 'Best First'.
Re^3: Tk fileevent 'readable' stops working by shmem (Chancellor) on Oct 23, 2007 at 12:15 UTC
Dunno what's wrong with it... I didn't dig much into Tk internals and have not time for that currently. But thinking again... do you attempt to bind the fileevent to the same widget? If so, that could be the gotcha. I don't know whether it is possible to bind multiple fileevents to the same widget, but I suspect it not being possible. --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]

Replies are listed 'Best First'.

Re^3: Tk fileevent 'readable' stops working
by shmem (Chancellor) on Oct 23, 2007 at 12:15 UTC

widget

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

[reply]