[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wresize and maxx/maxy short int overflow

From: Stephan Beal
Subject: Re: wresize and maxx/maxy short int overflow
Date: Mon, 2 Nov 2009 18:36:47 +0100

On Mon, Nov 2, 2009 at 3:29 PM, Katarina Machalkova <address@hidden> wrote:
maxy/maxx are short ints (NCURSES_SIZE_T, to be more precise), while wresize()
takes "normal" ints as params. Now I'm trying to make the window really big in
Y dimension by setting 'lines' param to value greater than 32 768.

Hi Katarina!

It is an error to create a WINDOW object larger than the screen. PAD objects may be larger, but WINDOWs cannot (if i'm not mistaken). Looking at the man pages, i cannot find this documented, but i "seem to remember" reading it somewhere. In fact, the X/Open standard defines _no_ error conditions for newwin() (which is really dumb, IMO). The man pages do say:

Special windows called pads may also be manipulated.  These are windows which are not constrained  to  the  size  of  the screen and whose contents need not be completely displayed.  See pad(3NCURSES) for more information.

which implies that WINDOWs may not be larger than the screen.

The above prints:
One: 3 22
Two: -22207 22

A quick look at the PAD API (man pad) shows that those functions do take "int" arguments.

----- stephan beal

reply via email to

[Prev in Thread] Current Thread [Next in Thread]