Re: curses: Visible cursor not set with wmove

To: Carsten Kunze <carsten.kunze%arcor.de@localhost>
Subject: Re: curses: Visible cursor not set with wmove
From: Brett Lymn <blymn%internode.on.net@localhost>
Date: Thu, 3 Nov 2016 10:07:21 +1030

On Fri, Sep 30, 2016 at 05:54:30PM +0200, Carsten Kunze wrote:
> 
> in an application I use two non-overlapping windows which fill the whole screen. Normally I hide the cursor (curs_set(0)), but for inputs I set curs_set(1). But the cursor does stay in stdscr position 0,0. If I use move() instead of wmove(), the cursor is positioned correctly. Also wmove() does work with ncurses correctly.
> 
Can you provide source code for a small program that demonstrates the
issue?
> I use an old NetBSD-"current" from Feb 28, maybe this is fixed now. Anyway--is this a known bug for NetBSD curses?
> 
It may be a bug or it may be correct behaviour - we need to check the
specifications. The fact that it behaves differently in ncurses is not
necessarily an indication we have a bug - the ncurses implementation may
be bugged :)
-- 
Brett Lymn

References:
- curses: Visible cursor not set with wmove
  - From: Carsten Kunze

Prev by Date: Re: [patch] fixes for rc.d/postfix
Next by Date: Re: curses: wmove(window, ...) doesn't set physical cursor
Previous by Thread: curses: Visible cursor not set with wmove
Next by Thread: curses: wmove(window, ...) doesn't set physical cursor
Indexes:

Home | Main Index | Thread Index | Old Index