logging

logging — Program message log

Functions

Types and Values

Includes

#include <app/gwyapp.h>

Description

Functions

gwy_app_setup_logging()

void
gwy_app_setup_logging (GwyAppLoggingFlags flags);

Sets up Gwyddion GLib log handler.

The log handler sends the messages to a log file or console, as Gwyddion usually does. This function may not be useful in Gwyddion-based programs unless they try to emulate Gwyddion behaviour closely.

Parameters

flags

Flags controlling how messages are handled.

 

gwy_app_set_log_messages()

void
gwy_app_set_log_messages (const gchar *domain,
                          GLogLevelFlags log_levels,
                          gboolean setting);

gwy_app_get_log_text_buffer()

GtkTextBuffer *
gwy_app_get_log_text_buffer (void);

Obtains a text buffer with program log messages.

This functions may only be called after gwy_app_setup_logging() and, obviously, after GTK+ was intialised.

The text buffer is owned by the library and must not be modified nor destroyed. It will be already filled with messages occurring between gwy_app_setup_logging() and this function call. New messages will be appended to the buffer as they arrive.

Returns

Text buffer with the program log messages.

Types and Values

enum GwyAppLoggingFlags

Flags controlling where program messages are written.

Members

GWY_APP_LOGGING_TO_FILE

Messages go to a log file, either gwyddion.log or given by environment variable GWYDDION_LOGFILE.

 

GWY_APP_LOGGING_TO_CONSOLE

Messages go to standard output and standard error depending on message type (emulating where GLib sends them).