endwin() doesn't exit (obviously) nor does it handle STDOUT/STDERR/STDIN data. Your
printed statements are stored by the shell until it is able to print them, namely when your program "let's go" of the terminal. If you redirect STDOUT to a file, you'd see that it appears immediately. It would be best if you could use the Curses calls instead of printing, since that is the point of Curses, but if you decide that you can't do that, try a wrefresh() after the print output AND unbuffer STDOUT. It's usually best to avoid endwin() since it means you wish to leave the pretty Curses environment. I have never found the need to do that- perhaps if you provide an example of why you'd need to do this....
If you need printf capability, use printw(). As always, hit your local docs- of which, currently, the C versions are far more complete.
AgentM Systems nor Nasca Enterprises nor
Bone::Easy nor Macperl is responsible for the
comments made by
AgentM. Remember, you can build any logical system with NOR.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.