[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Re: using 'select' with 'ncurses']
From: |
TRAVIS LOYD |
Subject: |
Re: [Re: using 'select' with 'ncurses'] |
Date: |
21 Jun 2001 10:51:13 MDT |
>> stdin & a socket. If I try to use ncurses calls instead of select I
>> get a blocked socket.
>stdin is a buffered file "stream" and a socket is a raw file descriptor.
>Try to separate your application in a client part (the ncurses stuff)
>and a server part, doing all socket communication and have
>them talking to each other.
I'm not sure what you mean. I have a server which is running and
am trying to write a client which uses ncurses to test it out.
Because using ncurses functions to read from stdin causes network data to be
ignored till data is entered (allowing for a network timeout to occur) I
attempted to use the "select" function to continually watch both stdin & the
open socket to the server. But "select" doesn't appear to work with ncurses
for some reason?
Using "fileno(stdin)" along with "select" didn't appear to make a difference.
Any other ideas? Maybe someone knows why "select" & "ncurses" aren't mingling
well?
Travis
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Re: using 'select' with 'ncurses'],
TRAVIS LOYD <=