dalegass@dalcsug.UUCP (Dale Michael Gass) (11/15/87)
Having a bit of a problem with curses... It seems that after resuming from a ^Z suspension, curses behaves very poorly, often writing many spaces out to the end of line, rather than using clear_to_end_of_line.... When I perform a refresh(curscr) to refresh the screen at any point after the resumption, it literally rewrites every single letter on the screen, even if the screen is completely filled with spaces--very sluggish... I was just wondering if anybody else has had a similar experience with curses... Any comments would be greatly appreciated. I should mention that the program that this is occuring in uses SIGIO interrupts on sockets. Don't know if this is a contributing factor or not... We refresh windows during these interrupts, so we make use of a specialized refresh routine which turns off incoming interrupts during the screen refresh (to avoid curses getting confused by layered [interrupted] wrefresh'es). When curses automatically refreshes the screen after ^Z, it uses the old wrefresh(), and interrupts might be occuring during this (in which nested wrefresh's might occur)... Is there any way of disabling curse's automatic refresh, so we can use our specialized wrefresh (turning off interrupts) in a SIGRSM trap? dalegass@dalcsug.uucp