RE: strange refreshing behavior with mvaddch()/mvaddstr()

[FRIEDLEY, ANDREW]

yes I added the clear() call in that loop to demonstrate the flickering
i am seeing in my actual program. in my actual program i am not
clear()'ing the screen but rather drawing some text, and drawing some
more text on top of it (a GUI menu).  The flickering i see in my program
alternates between the text under the menu and the actual menu.  if you
take out the clear in that test program that loop would be drawing hte
same data thats already there and you cant see the flicker as easily in
this instance - doesnt really fix the problem :)

andrew friedley


-----Original Message-----
From: Thomas Dickey [mailto:address@hidden
Sent: Friday, August 31, 2001 4:32 AM
To: FRIEDLEY, ANDREW
Cc: address@hidden
Subject: Re: strange refreshing behavior with mvaddch()/mvaddstr()


On Thu, Aug 30, 2001 at 08:11:38PM -0500, FRIEDLEY, ANDREW wrote:
> alright thanks. you wouldnt happen to know a way around this would
you?
> 
> (sorry for double sending to brian)
> 
> -----Original Message-----
> From: Brian Raiter [mailto:address@hidden
> Sent: Thursday, August 30, 2001 7:44 PM
> To: address@hidden
> Subject: Re: strange refreshing behavior with mvaddch()/mvaddstr()
> 
> 
> > My problem is, whenever I change the contents of stdscr, the screen
> > refreshes just as if i called refresh().  I am only using mvaddch()
> and
> > mvaddstr(), and waddch(stdscr, blah) to draw.
> 
> ... and wgetch(). From the wgetch man page:
> 
>        If the window is not a pad, and it has been moved or modified
>        since the last call to wrefresh, wrefresh will be called before
>        another character is read.

the flicker is produced by the 'clear()' call (man wclear):

       The  clear  and wclear routines are like erase and werase,
       but they also call clearok, so that the screen is  cleared
       completely  on  the  next call to wrefresh for that window
       and repainted from scratch.

for the effect you're trying to produce, clrtoeol() or clrtobot() would
be better.

-- 
Thomas E. Dickey <address@hidden>
http://dickey.his.com
ftp://dickey.his.com