From dfdb8a6de3b737fcfdee6c3ca836c730e2ef83a6 Mon Sep 17 00:00:00 2001 From: Darrell Anderson Date: Mon, 6 Jan 2014 02:24:46 +0100 Subject: Rename kdebugdialog -> tdedebugdialog --- .../docs/tdebase/tdedebugdialog/index.docbook | 206 +++++++++++++++++++++ 1 file changed, 206 insertions(+) create mode 100644 tde-i18n-en_GB/docs/tdebase/tdedebugdialog/index.docbook (limited to 'tde-i18n-en_GB/docs/tdebase/tdedebugdialog/index.docbook') diff --git a/tde-i18n-en_GB/docs/tdebase/tdedebugdialog/index.docbook b/tde-i18n-en_GB/docs/tdebase/tdedebugdialog/index.docbook new file mode 100644 index 00000000000..da8a975e139 --- /dev/null +++ b/tde-i18n-en_GB/docs/tdebase/tdedebugdialog/index.docbook @@ -0,0 +1,206 @@ + +TDEDebugDialog"> + + + + + +]> + + + +The &tdedebugdialog; Handbook + + +&David.Faure; &David.Faure.mail; +MalcolmHunter
malcolm.hunter@gmx.co.uk
Conversion to British English + + +2001-02-13 +0.03.00 + + +This document describes &tdedebugdialog;. + + + +KDE +TDEDebugdialog + + + + +What is TDEDebugDialog? + +It is a dialogue box for managing diagnostic messages at runtime. + +If you simply start tdedebugdialog, you will see a list of areas, that can be disabled or enabled. A kdDebug(area) call in the code will show something in the debug output only if the area is enabled. + +Note that kdWarning, kdError and kdFatal always appear, they are NOT controlled by this setting. + + + +Area + +The areas which should only be output. Every message that is not mentioned here will simply not be output (unless this field remains empty, which is the default, and means that all messages should be output). You can enter several areas separated by commas here, and you can also use area ranges with the syntax start-end. Thus a valid entry could be: 117,214-289,356-359,221. Do not use whitespaces. + + + + +If you start tdedebugdialog , then for every severity level you can define separately what should be done with the diagnostic messages of that level, and the same for each debug area. + +In full mode, first you should select the debug area you are interested in from the drop down list at the top. + +You may independently set the output for various types of messages: + + +Information +Warning +Error +Fatal Error + + +For each of these types, you can set the following: + + + +Output to: + +In this Combobox, you can choose where the messages should be output. The choices are: File, Message Box, Shell (meaning stderr) and Syslog. Please do not direct fatal messages to syslog unless you are the system administrator yourself. The default is Message Box. + + + + +Filename: +This is only enabled when you have chosen File as the output and provides the name of that file (which is interpreted as relative to the current folder). The default is kdebug.dbg. + + + + +Apart from this, you can also tick the checkbox Abort on fatal errors. In this case, if a diagnostic message with the severity level KDEBUG_FATAL is output, the application aborts with a SIGABRT after outputting the message. + +When you close the dialogue by pressing OK, your entries apply immediately and are saved in kdebugrc. When you press Cancel, your entries are discarded and the old ones are restored. + +Credits to Kalle Dalheimer for the original version of &tdedebugdialog; + + + +&documentation.index; + + + + -- cgit v1.2.1