Bug 233488

Description of problem:

programs using the mouse click feature of ncurses act crazy when run from
within /usr/bin/screen. When mousemask() is used after initscr() in a
ncurses-based program, getch() will go crazy. See example code below.

Version-Release number of selected component (if applicable):

ncurses-5.5-24.20060715
ncurses-devel-5.5-24.20060715
screen-4.0.3-2.fc6

How reproducible:

by compiling and executing the following example code (cursebug.c):

#include <stdio.h>
#include <ncurses.h>

int main(int argc, char **argv) {

    initscr();

    mousemask(BUTTON1_PRESSED | BUTTON1_CLICKED, NULL);

    halfdelay(10);

    for (;;) {
        int key = getch();
        switch (key) {
            case 'q':
            case 'Q':
                return 0;
            case KEY_MOUSE:
                fprintf(stderr, "Mouse Click.\n");
                break;
            default:
                fprintf(stderr, "default: key = %d\n", key);
                break;
        }
    }

    endwin();

    return 0;
}

Steps to Reproduce:
1. compile code: gcc -o cursebug cursebug.c -Wall -lncurses
2. in a window, start screen: /usr/bin/screen
3. then, start example from within screen: ./cursebug 2>cursebug.log
3. in a separate window, view log: tail -f cursebug.log
  
Actual results:

getch() returns -1 in a very tight loop

Expected results:

getch() should return -1 once every second (as per halfdelay(10)), and
actual key presses and mouse clicks when entered. This works fine when
example is run directly from console or an xterm, but not from within
screen.

Additional info: