Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site tesla.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxz!vax135!cornell!tesla!mac
From: mac@tesla.UUCP (Michael Mc Namara)
Newsgroups: net.unix-wizards
Subject: Re: A Question About CURSES Capabilities
Message-ID: <418@tesla.UUCP>
Date: Sun, 5-Aug-84 00:14:16 EDT
Article-I.D.: tesla.418
Posted: Sun Aug  5 00:14:16 1984
Date-Received: Mon, 6-Aug-84 01:20:00 EDT
References: <19781@wivax.UUCP>
Organization: Cornell Electrical Eng.
Lines: 25


>If the termcap database defines the delete line capability, shouldn't curses
>use it if the deleteln() function is used?  Curses is repainting the entire
>screen.  Could my curses code be old, it's from 1981.
>
>Also, if I update the curses window buffers using deleteln() and I manually
>update the screen by outputting the delete line string from termcaps, if it
>exists, how do I convince curses that the screen is up-to-date so that the
>next refresh doesn't repaint the screen.  Is there a flag somewhere?
>
>                          Rudy Bazelman / Wang Institute
>
>

The flag you want to use is idlok(win,bf).

"If enabled,  curses will consider using the hardware insert/delete line 
feature of terminals so equipped.   If disabled, curses will  never use 
this feature. " -- The Curses Reference Manual.

This should answer both queries.

                             Michael McNamara @ Cornell EE.
                            ..!cornell!tesla!mac