OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [insight/] [tk/] [doc/] [tkerror.n] - Blame information for rev 1765

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 578 markom
'\"
2
'\" Copyright (c) 1990-1994 The Regents of the University of California.
3
'\" Copyright (c) 1994-1996 Sun Microsystems, Inc.
4
'\"
5
'\" See the file "license.terms" for information on usage and redistribution
6
'\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
7
'\"
8
'\" RCS: @(#) $Id: tkerror.n,v 1.1.1.1 2002-01-16 10:25:49 markom Exp $
9
'\"
10
.so man.macros
11
.TH tkerror n 4.1 Tk "Tk Built-In Commands"
12
.BS
13
'\" Note:  do not modify the .SH NAME line immediately below!
14
.SH NAME
15
tkerror \- Command invoked to process background errors
16
.SH SYNOPSIS
17
\fBtkerror \fImessage\fR
18
.BE
19
 
20
.SH DESCRIPTION
21
.PP
22
Note: as of Tk 4.1 the \fBtkerror\fR command has been renamed to
23
\fBbgerror\fR because the event loop (which is what usually invokes
24
it) is now part of Tcl.  For backward compatibility
25
the \fBbgerror\fR provided by the current Tk version still
26
tries to call \fBtkerror\fR if there is one (or an auto loadable one),
27
so old script defining that error handler should still work, but you
28
should anyhow modify your scripts to use \fBbgerror\fR instead
29
of \fBtkerror\fR because that support for the old name might vanish
30
in the near future. If that call fails, \fBbgerror\fR
31
posts a dialog showing the error and offering to see the stack trace
32
to the user. If you want your own error management you should
33
directly override \fBbgerror\fR instead of \fBtkerror\fR.
34
Documentation for \fBbgerror\fR is available as part of Tcl's
35
documentation.
36
 
37
.SH KEYWORDS
38
background error, reporting

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.