bug-ncurses
[Top][All Lists]
Advanced

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

Re: Cursor not working with pads.


From: Josh_Bresben
Subject: Re: Cursor not working with pads.
Date: Thu, 6 Dec 2012 18:49:14 -0800 (PST)

Sorry to send another message but I am really desperate to figure this issue
out. I've tried so many different things to no avail. I won't send another
message after this but I thought I would try again. The link to the code
with the problem is in the previous post I made.


Josh_Bresben wrote:
> 
> Thanks for responding, the following code is a stripped down version of
> the code that is causing the problem. As stated,
> the problem is that I am manually setting the cursor with wmove() in this
> code but the visual cursor stays at (0,0). Thanks for any advice you give
> with regards to resolving this issue. It's really bugging me.
> 
>  http://pastebin.com/r12eTyeV Here is a link to the pasted code. 
> 
> 
> Thomas Dickey-2 wrote:
>> 
>> 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>
>> http://invisible-island.net
>> ftp://invisible-island.net
>> 
>>  
>> _______________________________________________
>> Bug-ncurses mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/bug-ncurses
>> 
>> 
> 

-- 
View this message in context: 
http://old.nabble.com/Cursor-not-working-with-pads.-tp34750145p34769233.html
Sent from the Gnu - Ncurses mailing list archive at Nabble.com.




reply via email to

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