callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Don't use g_print for debug output

Browse Source 
The g_print documentation explicitly says not to do this, since
g_print is meant to be redirected by applications. Instead use
g_message for logging that can be triggered via GTK_DEBUG.
This commit is contained in:
Matthias Clasen
2016-02-28 15:33:18 -05:00
parent 0ac71e81cf
commit 2ee7fb1818
11 changed files with 154 additions and 132 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
gtk/gtkbuilderparser.c
View File

@ -318,8 +318,9 @@ parse_object (GMarkupParseContext *context,
{
data->requested_object_level = data->cur_object_level;
GTK_NOTE (BUILDER, g_print ("requested object \"%s\" found at level %d\n",
object_id, data->requested_object_level));
GTK_NOTE (BUILDER,
g_message ("requested object \"%s\" found at level %d",
object_id, data->requested_object_level));
data->inside_requested_object = TRUE;
}
@ -937,7 +938,7 @@ start_element (GMarkupParseContext *context,
g_string_insert_c (tags, 0, ' ');
g_string_truncate (tags, tags->len - 1);
}
g_print ("<%s%s>\n", element_name, tags->str);
g_message ("<%s%s>", element_name, tags->str);
g_string_free (tags, TRUE);
}
#endif
@ -1008,7 +1009,7 @@ end_element (GMarkupParseContext *context,
{
ParserData *data = (ParserData*)user_data;
GTK_NOTE (BUILDER, g_print ("</%s>\n", element_name));
GTK_NOTE (BUILDER, g_message ("</%s>", element_name));
if (data->subparser && data->subparser->start)
{
@ -1060,8 +1061,9 @@ end_element (GMarkupParseContext *context,
if (data->requested_objects && data->inside_requested_object &&
(data->cur_object_level == data->requested_object_level))
{
GTK_NOTE (BUILDER, g_print ("requested object end found at level %d\n",
data->requested_object_level));
GTK_NOTE (BUILDER,
g_message ("requested object end found at level %d",
data->requested_object_level));
data->inside_requested_object = FALSE;
}