Non-blocking user input in loop without ncurses_hunspell has been compiled without ncurses user in-CSDN博客

Non-blocking user input in loop without ncurses

The title sounds a bit awkward, let my briefly explain what is it all about.

In my program, I want to wait for user input, but at the same time, I want my other operations keep continue processing.That I define it as non-blocking user input. I want my program to wait for user input in the loop, if receives user input process it and continue wait for next user input, else continue processing other circular operations.

Usually, people will think about using ncurses library. By using ncurses, you can easily perform non-blocking user input using timeout(0) and getch(). Refers to thencurses matrix for references.

What if I don’t want to uses ncurses? Its there any alternatives? Sometimes I just wanna add a function which need non-blocking in a large program, I don’t want to use ncurses because it makes my print line acts differently, or some other reason.

I have figure out a way, thanks to programmers at ##c@irc.freenode.net. It might look messy and complected, but it works the way I wanted. I uses functions of termios and select, lets look at the functions one by one.

int NoBlocking_Read()
{
    struct timeval tTV;
    fd_set tFDs;
	
    tTV.tv_sec = 0;
    tTV.tv_usec = 0;
    FD_ZERO(&tFDs);	
    FD_SET(STDIN_FILENO, &tFDs); 
    select(STDIN_FILENO+1, &tFDs, NULL, NULL, &tTV);
    return FD_ISSET(STDIN_FILENO, &tFDs);
}

This function perform non-blocking checking on the standard input (stdin) without timeout 0, tv.tv_sec and tv.tv_usec both set to zero. select usually uses in the case where there have multiple I/O need to process, or check at the same time. But in this case, I only interested in standard input, therefore only one FD_SET(STDIN_FILENO, &fds) is trigger. For select parameters details, please check out the manual.Seems we are only interested in input, so we place out fd set at second parameter of select(), the 3rd is for output and 4th is for exception.

Important part, after select if user input is trigger, FD_ISSET will return non zero value, else return 0. So, we now can use it like this:

<span style="font-size:18px;">while( 0 == NoBlocking_Read() )
{

}</span>

Due to the canonical mode (标准模式)of your terminal,you need to hit enter to confirm your user input. Canonical mode means it always wait for enter to confirms the user input. If that is not your case, bellow is another function to cater that.

int  NoBlocking_Init()
{
    struct termios tTTYState;
 
    //get the terminal state
    tcgetattr(STDIN_FILENO, &tTTYState);
 
    //turn off canonical mode
    tTTYState.c_lflag &= ~ICANON;
    //minimum of number input read.
    tTTYState.c_cc[VMIN] = 1;   /* 有一个数据时就立刻返回 */

    //set the terminal attributes.
    tcsetattr(STDIN_FILENO, TCSANOW, &tTTYState);

    return 0;
}

void NoBlocking_Exit()
{
    struct termios tTTYState;
 
    //get the terminal state
    tcgetattr(STDIN_FILENO, &tTTYState);
 
    //turn on canonical mode
    tTTYState.c_lflag |= ICANON;
	
    //set the terminal attributes.
    tcsetattr(STDIN_FILENO, TCSANOW, &tTTYState);
}

The function name might be misleading, what the function actually does is turn off the canonical mode for stdin. First, get the states of stdin of term. Next turn off the canonical by set 0 to the bits. The line of ttystate.c_cc[VMIN] is set the minimum number of user input to accept. If you set it as 2, the select will wait until 2 character is given, then it will capture as input. At last set the term state. The function actually does allow you to turn on and off the canonical mode.

Okay, Let see how it apply to work

int main()
{ 
	char c = 0;
	NoBlocking_Init();
	while( 0 == NoBlocking_Read() )
	{
		usleep(1);
		c = fgetc(stdin);
		if(c == 'q')
		{
			exit(0);
		}
		switch (c)
		{
			case 'u':
			{
				break;
			}
			case 'd':
			{
				break;
			}			
		}		
	}	
}

Press ‘q’ will lead the program to quit, else you will see the print of ’0′ overwhelming the screen. Observed that I am using usleep(1) inside the loop, without putting usleep, the programs is more responsive, but it uses high CPU resources. On the other hand, putting usleep(1) reduces the CPU resources and also decreases responsiveness of the program. Depend on your needs, you may choose to put it in or not.

I have make the comparison between this application and a simple ncurses program, this program seems to use lesser memory. Couldn’t measure for CPU resources, as bothps and top shows 0.0 %.