Subject: Re: ncurses getyx() quickie
To: None <tooleym@Douglas.BC.CA>
From: Brad Salai <bsalai@law.roc.servtech.com>
List: netbsd-help
Date: 03/15/1998 14:06:58
tooleym@Douglas.BC.CA wrote:

> It was my fault--I read the ncurses man page which instructs me to include
> <curses.h> -- which apparently is for the OLD curses package. I had to
> -I/usr/pkg/include and include <ncurses.h> , which cleared things up
> perfectly. :) Everything works well now, thanks for the responses. Dang
> man pages..! :)

You are going to send-pr, right, so others will benefit?

> Marc Tooley
> tooleym@douglas.bc.ca (thank god soon I can retire this one)
> P.S. The behaviour of using the old curses.h included a HUGE value being
> stuffed into y, and a zero value being stuffed into x. Probably a
> relocation or redefined set of globals, but since it works for me now,
> I'll just remember what had to be done and chalk it up to a minor
> annoyance. :) Very minor. Almost not worth mentioning. Which is why I'm
> writing this note, eh?
>
> > > How the heck am I supposed to use getyx()?
> > >
> > > I've tried:
> > >
> > > getyx(mywin, county, countx);
> >
> > AFAIK, that's how you are supposed to use it.  You pass it a WINDOW * and
> > two int's.  The window is a handle you've got from newwin() and the y and
> > x position are placed into the two int's.
> >
> > What happens when you do this?
> >
> > J
> >
> > PS.  I've only done this using BSD curses but I don't see why it should
> > be different using ncurses.



--
Brad Salai                      bsalai@tmonline.com
Cumpston & Shaw
Two State St.
Rochester, NY 14526