in reply to Re: Curses.pm with Term::ANSIColor
in thread Curses.pm with Term::ANSIColor

I'll try this right away, having just gotten Curses.pm patched to build with 5.8 and threading.

Replies are listed 'Best First'.
Re: Re: Re: Curses.pm with Term::ANSIColor
by Llew_Llaw_Gyffes (Scribe) on May 07, 2003 at 03:58 UTC
    has_colors() is indeed lying. However, Term::ANSIColor still does not work in a curses window, when Curses color does. So I guess I get to rewrite all the color code for the interactive portion of the program to do its colors that way.
      Just so you know, when you activate a Curses "screen", most normal screen I/O won't work right, something that will create problems if, say, your application calls die() or uses any other functions that do screen I/O that don't understand Curses. When writing curses applications, it's usefil to put calls to endwin() right before all your die()s (and of course, before your application exits).
        Oh, hey, I just came back and found this reply. Yes, I'm using endwin() and all appropriate other things to make icbm clean up after itself. (1.0 shipped back in February, by the way.)