luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-04 10:16:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

updated a bit more.

Browse Source 
2000-06-11  Damon Chaplin  <damon@helixcode.com>

	* tmpl/messages.sgml: updated a bit more.
This commit is contained in:
Damon Chaplin 2000-06-11 18:32:13 +00:00 committed by Damon Chaplin
parent 2c4d8d1ae2
commit 876a6767eb
3 changed files with 16 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/ChangeLog
View File

@ -1,3 +1,7 @@
2000-06-11 Damon Chaplin <damon@helixcode.com>
* tmpl/messages.sgml: updated a bit more.
2000-06-11 Damon Chaplin <damon@helixcode.com>
* tmpl/messages.sgml: updated a few bits about log handlers & flags.

4
docs/reference/glib/glib/ChangeLog
View File

@ -1,3 +1,7 @@
2000-06-11 Damon Chaplin <damon@helixcode.com>
* tmpl/messages.sgml: updated a bit more.
2000-06-11 Damon Chaplin <damon@helixcode.com>
* tmpl/messages.sgml: updated a few bits about log handlers & flags.

11
docs/reference/glib/tmpl/messages.sgml
View File

@ -154,8 +154,13 @@ documentation.
<!-- ##### FUNCTION g_log_set_handler ##### -->
<para>
Sets the log handler for a domain and a set of log levels.
Note that to handle fatal and recursive messages the @log_levels parameter
To handle fatal and recursive messages the @log_levels parameter
must be combined with the G_LOG_FLAG_FATAL and G_LOG_FLAG_RECURSIVE bit flags.
</para>
<para>
Note that since the G_LOG_LEVEL_ERROR log level is always fatal, if you want
to set a handler for this log level you must combine it with G_LOG_FLAG_FATAL.
</para>
<example>
<title>Adding a log handler for all warning messages</title>
@ -168,8 +173,8 @@ must be combined with the G_LOG_FLAG_FATAL and G_LOG_FLAG_RECURSIVE bit flags.
@log_domain: the log domain, or NULL for the default "" application domain.
@log_levels: the log levels to apply the log handler for. To handle fatal
and recursive messages as well, comine the log levels with the G_LOG_FLAG_FATAL
and G_LOG_FLAG_RECURSIVE bit flags.
and recursive messages as well, combine the log levels with the
G_LOG_FLAG_FATAL and G_LOG_FLAG_RECURSIVE bit flags.
@log_func: the log handler function.
@user_data: data passed to the log handler.
@Returns: the id of the new handler.