-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<!--
****************************************************************************
- * Copyright (c) 2000-2005,2007 Free Software Foundation, Inc. *
+ * Copyright (c) 2000-2009,2010 Free Software Foundation, Inc. *
* *
* Permission is hereby granted, free of charge, to any person obtaining a *
* copy of this software and associated documentation files (the *
* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
- * @Id: curs_trace.3x,v 1.8 2007/02/24 17:33:49 tom Exp @
+ * @Id: curs_trace.3x,v 1.12 2010/12/04 18:40:45 tom Exp @
-->
<HTML>
<HEAD>
</PRE>
<H2>NAME</H2><PRE>
<STRONG>_tracef</STRONG>, <STRONG>_tracedump</STRONG>, <STRONG>_traceattr</STRONG>, <STRONG>_traceattr2</STRONG>,
- <STRONG>_nc_tracebits</STRONG>, <STRONG>_tracechar</STRONG>, <STRONG>_tracechtype</STRONG>, <STRONG>_tracechtype2</STRONG>,
- <STRONG>_tracemouse</STRONG>, <STRONG>trace</STRONG> - <STRONG>curses</STRONG> debugging routines
+ <STRONG>_nc_tracebits</STRONG>, <STRONG>_tracecchar_t</STRONG>, <STRONG>_tracecchar_t2</STRONG>, <STRONG>_tracechar</STRONG>,
+ <STRONG>_tracechtype</STRONG>, <STRONG>_tracechtype2</STRONG>, <STRONG>_tracemouse</STRONG>, <STRONG>trace</STRONG> - <STRONG>curses</STRONG>
+ debugging routines
</PRE>
<STRONG>char</STRONG> <STRONG>*_traceattr(attr_t</STRONG> <STRONG>attr);</STRONG>
<STRONG>char</STRONG> <STRONG>*_traceattr2(int</STRONG> <STRONG>buffer,</STRONG> <STRONG>chtype</STRONG> <STRONG>ch);</STRONG>
<STRONG>char</STRONG> <STRONG>*_nc_tracebits(void);</STRONG>
- <STRONG>char</STRONG> <STRONG>*_tracechar(int);</STRONG>
+ <STRONG>char</STRONG> <STRONG>*</STRONG> <STRONG>_tracecchar_t(const</STRONG> <STRONG>cchar_t</STRONG> <STRONG>*string);</STRONG>
+ <STRONG>char</STRONG> <STRONG>*</STRONG> <STRONG>_tracecchar_t2(int</STRONG> <STRONG>buffer,</STRONG> <STRONG>const</STRONG> <STRONG>cchar_t</STRONG> <STRONG>*string);</STRONG>
+ <STRONG>char</STRONG> <STRONG>*_tracechar(int</STRONG> <STRONG>ch);</STRONG>
<STRONG>char</STRONG> <STRONG>*_tracechtype(chtype</STRONG> <STRONG>ch);</STRONG>
<STRONG>char</STRONG> <STRONG>*_tracechtype2(int</STRONG> <STRONG>buffer,</STRONG> <STRONG>chtype</STRONG> <STRONG>ch);</STRONG>
<STRONG>char</STRONG> <STRONG>*_tracemouse(const</STRONG> <STRONG>MEVENT</STRONG> <STRONG>*event);</STRONG>
</PRE>
<H2>DESCRIPTION</H2><PRE>
- The <STRONG>trace</STRONG> routines are used for debugging the ncurses li-
+ The <STRONG>trace</STRONG> routines are used for debugging the ncurses li-
braries, as well as applications which use the ncurses li-
braries. These functions are normally available only with
- the debugging library <EM>libncurses</EM><STRONG>_</STRONG><EM>g.a</EM>, but may be compiled
- into any model (shared, static, profile) by defining the
- symbol <STRONG>TRACE</STRONG>.
+ the debugging library <EM>libncurses</EM><STRONG>_</STRONG><EM>g.a</EM>, but may be compiled
+ into any model (shared, static, profile) by defining the
+ symbol <STRONG>TRACE</STRONG>. Additionally, some functions are only
+ available with the wide-character configuration of the li-
+ braries.
- The principal parts of this interface are the <STRONG>trace</STRONG> rou-
+ The principal parts of this interface are the <STRONG>trace</STRONG> rou-
tine which selectively enables different tracing features,
and the <STRONG>_tracef</STRONG> routine which writes formatted data to the
<EM>trace</EM> file.
- Calling <STRONG>trace</STRONG> with a nonzero parameter opens the file
- <STRONG>trace</STRONG> in the current directory for output. The parameter
+ Calling <STRONG>trace</STRONG> with a nonzero parameter opens the file
+ <STRONG>trace</STRONG> in the current directory for output. The parameter
is formed by OR'ing values from the list of <STRONG>TRACE_</STRONG><EM>xxx</EM> def-
initions in <STRONG><curses.h></STRONG>. These include:
trace all character outputs.
TRACE_ORDINARY
- trace all update actions. The old and new screen
- contents are written to the trace file for each re-
+ trace all update actions. The old and new screen
+ contents are written to the trace file for each re-
fresh.
TRACE_CALLS
rameter is nonzero. Some features overlap. The specific
names are used as a guideline.
+ These functions check the <STRONG>NCURSES_TRACE</STRONG> environment vari-
+ able, to set the tracing feature as if <STRONG>trace</STRONG> was called:
+ filter, initscr, new_prescr, newterm, nofilter,
+ ripoffline, setupterm, slk_init, tgetent
+
+
</PRE>
<H2>RETURN VALUE</H2><PRE>