[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: flashing screen symptoms (an example)
From: |
Neil Zanella |
Subject: |
Re: flashing screen symptoms (an example) |
Date: |
Fri, 3 Nov 2000 18:13:28 -0330 (NST) |
On Fri, 3 Nov 2000, Thomas Dickey wrote:
> That's basically because an application that doesn't keep track of the
> overlap between windows will try to repaint the whole screen to update
> things - that's a lot of output replacing the current contents with itself
> and things tend to flash on/off and flicker. The panel library is designed
> to do that (I don't do much with it, but the demos in ncurses seem to do
> what they're designed to do).
So what are subwindows good for when the panel library does exactly the
same thing with less flashing? I thought that the panel library must be
used with overlapping windows and that subwin and derwin on the other
hand could be used so long as every window overlaps with nothing but
stdscr. What is the truth here? When is it that subwindows should be
used as opposed to the panel library then?
Thanks,
Neil
- flashing screen symptoms (an example), Neil Zanella, 2000/11/03
- Re: flashing screen symptoms (an example), Thomas E. Dickey, 2000/11/03
- Re: flashing screen symptoms (an example), Neil Zanella, 2000/11/03
- Re: flashing screen symptoms (an example), Thomas Dickey, 2000/11/03
- Re: flashing screen symptoms (an example),
Neil Zanella <=
- Re: flashing screen symptoms (an example), Thomas Dickey, 2000/11/03
- Re: flashing screen symptoms (an example), Neil Zanella, 2000/11/03
- Re: flashing screen symptoms (an example), Thomas Dickey, 2000/11/03
- Re: flashing screen symptoms (an example), Neil Zanella, 2000/11/03
- Re: flashing screen symptoms (an example), Brian Raiter, 2000/11/03
- Re: flashing screen symptoms (an example), Neil Zanella, 2000/11/03
- Re: flashing screen symptoms (an example), Neil Zanella, 2000/11/03
- Re: flashing screen symptoms (an example), Thomas Dickey, 2000/11/04