Re: flashing screen symptoms (an example)

[Neil Zanella]

On Fri, 3 Nov 2000, Thomas Dickey wrote:

> On Fri, Nov 03, 2000 at 06:13:28PM -0330, Neil Zanella wrote:
> > 
> > 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
> 
> mainly for simple geometry management - keeping track of coordinates, and
> limiting the scope of output.  When you have to worry about overlapping
> windows, and deciding which should be repainted, then you should think
> about using the panel library.

But whenever a subwindow is created it overlaps with stdscr so what
exactly is the meaning of a nonoverlapping window? All of the windows
I am using have the following property:

given any two windows w1 and w2 exactly one of the following holds:

(i) w1 is entirely contained in w2
(ii) w2 is entirely contained in w1
(iii) w1 and w2 are entirely disjoint

is this equivalent to your definition of nonoverlapping windows
or are your nonoverlapping windows subwindows of stdscr with no
other windows in between? My reasons for using subwindows include
the following:

(i) to establish separate coordinate systems
(ii) to maintain different default backgrounds in different places
(iii) to limit the scope of output, yes, this too
(iv) to allow independent scrolling of windows

But then I get that flickering. So why is this not working properly?

Thanks,

Neil