[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: flashing screen symptoms (an example)
From: |
Brian Raiter |
Subject: |
Re: flashing screen symptoms (an example) |
Date: |
Fri, 3 Nov 2000 17:25:34 -0800 |
> But whenever a subwindow is created it overlaps with stdscr so what
> exactly is the meaning of a nonoverlapping window?
>From the ncurses man page:
Note that curses does not handle overlapping windows,
that's done by the panel(3X) library. This means that you
can either use stdscr or divide the screen into tiled win-
dows and not using stdscr at all. Mixing the two will
result in unpredictable, and undesired, effects.
In other words, you *can* have two windows that overlap (such as
stdscr and a subwindow), as long as you only draw on, and refresh, one
of them.
For my part, I've generally found it simpler to just use stdscr and
calculate the coordinates of subregions in the code, or to go all the
way and use panels. Using tiled subwindows usually makes for more
complicated code in the end.
b
- 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, 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), Thomas Dickey, 2000/11/03
- Re: flashing screen symptoms (an example), Neil Zanella, 2000/11/03
- Re: flashing screen symptoms (an example),
Brian Raiter <=
- 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