[Top][All Lists]

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

Re: Cursor not working with pads.

From: Thomas Dickey
Subject: Re: Cursor not working with pads.
Date: Tue, 04 Dec 2012 03:59:54 -0500
User-agent: Mutt/1.5.20 (2009-06-14)

On Mon, Dec 03, 2012 at 08:15:25PM -0800, Josh_Bresben wrote:
> Hello,
> I've set up a pad that I use to scroll to different content by calls to
> prefresh(). Everything about the pad works except for one visual issue: I am
> able to logically set the cursor to be in the proper subpads of the main
> scrollable pad (i.e. areas where the user can type) by calling wmove(); that
> works just fine. However, the visual blinking cursor that actually lets the
> user know where he/she is remains at the origin (0,0).
> I've even tried taking out all calls to wmove() and making the visual cursor
> move to a random spot like (4,9) and then calling refresh(), but the visual
> cursor just stays at the origin. Is there something extra that I have to do
> when using pads in order to get cursor movement functioning correctly?

The usual reason for the cursor appearing in the wrong place is from
using getch() rather than wgetch().  The latter allows you to specify
the window from which input should happen.  If it's not that simple,
a short program demonstrating the problem would be helpful.

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

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