[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
end thread select & ncurses
From: |
Travis W. Loyd |
Subject: |
end thread select & ncurses |
Date: |
Thu, 21 Jun 2001 15:53:04 -0700 |
User-agent: |
Mutt/1.2.5i |
I was ready to hunt down for ncurses gurus when I encountered the problem with
select & ncurses this time only because I struggled so hard in the past only to
fail.
This time however I may have jumped the gun. With my current experience I was
able to change my thinking and use the ncurses funtions to recieve data without
blocking a select command which looks for network data. (Select may even be
taken out completely of course.)
It might not be a bad idea to metion that using stdin w/ select will not work
with ncurses but that a sutable solution is to use getch with nobreak on & a
fast timeout w/ select. Maybe a good place would be in the getch man page.
I can say I've tried this 3 times only to succeed this time. (Before I thought
select was the only way to monitor multiple inputs.) I can't be alone in doing
this. Those three times were seperated by approximately 1.75 years.
Thanks for everyone's quick help on the subject.
--
Travis
- end thread select & ncurses,
Travis W. Loyd <=