From: fortony@sonne.cso.uiuc.edu Subject: Re: curses Date: 2 Aug 1992 05:34:13 GMT
hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
>In article <fortony.712630133@murphy>, fortony@sonne.cso.uiuc.edu writes:
>|>
>|> Is anyone else having problems with curses? I've written a very short
>|> program which should move an x up, down, left and right on the screen
>|> depending on what key the user presses, but there are two problems:
>|>
>|> 1) sometimes, the x is written to the wrong place entirely (8 spaces
>|> to the right of where it should, for instance)
>|>
>|> 2) endwin() invariably returns a non-zero value.
>|>
>Please take a look at the curse code. endwin () returns some garbage.
>I believe lots of bsd code do something like this,
Alright. I don't have the sources, but it looks increasingly like I'll
need to get them to do serious development. The man pages I have (from
another machine and operating system) indicate that endwin() returns
a value. These man pages also indicate that there are predefined
attribute constants, however, (like ACS_BOLD), which don't exist under
Linux. I guessed wrong, I suppose.
The problem I forgot to mention under endwin(): the function doesn't
do what it is rumored to; it is supposed to clean up after curses,
but it leaves the screen alone.
>I tried to clear libinet.a in gcc 2.2.2d. I didn't get time for curses.
I'm sorry, I don't understand what this means. Thanks for the reply,
though.
>--
>H.J.
>Gcc/libc maintainer for Linux.
-- a b c d e f g h i j k l m n o p q r s t u v w x y z Felix Sebastian Ortony fortony@murphy.gis.uiuc.edu