> You might be trying to write to a section that is currently off
> screen.
Bingo. I *thought* I was okay, but I wasn't refreshing until the
end of the display loop, so I never saw all the addstr() calls that
had succeeded but which had yet to be painted. Adding a refresh()
call in the loop expo
> Maybe the Solaris 10 curses stuff is toast?
Maybe. the curses and curses_panel modules were linked against crufty stuff in
/usr/lib. I've asked our admins to install ncurses. Hopefully that's the cure.
Skip
--
http://mail.python.org/mailman/listinfo/python-list
> I have a fairly simple curses app which is giving me this error:
>
> addstr() returned ERR
I tried something else. Using both python 2.4 and SVN head (aka 2.6a0 sort of)
I tried the curses regression test. Both versions crashed, though with somewhat
different errors. Maybe the Solaris 10
>> screen.addstr(row, 39, "|")
>>
>> where row is 3.
Ian> You might be trying to write to a section that is currently off
Ian> screen. Seems to me when I was doing some curses stuff that when I
Ian> tried to write to one more row than could be fit onto my terminal
Ia
On 5/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have a fairly simple curses app which is giving me this error:
>
> addstr() returned ERR
>
> I'm trapping it and continuing. I can see that *some* of my addstring calls
> succeed. This one happens to be
>
> screen.addstr(row, 39,
I have a fairly simple curses app which is giving me this error:
addstr() returned ERR
I'm trapping it and continuing. I can see that *some* of my addstring calls
succeed. This one happens to be
screen.addstr(row, 39, "|")
where row is 3. After the screen was cleared two other calls
