After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 331797 - Startup errors should be handled
Startup errors should be handled
Status: RESOLVED OBSOLETE
Product: glade
Classification: Applications
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks: 595075
 
 
Reported: 2006-02-19 17:37 UTC by Tristan Van Berkom
Modified: 2018-03-26 14:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tristan Van Berkom 2006-02-19 17:37:03 UTC
This is a very simple exersize and a perfect opportunity to
get familliar with the glade-3 core :)

Basicly we need to detect semi-critical and critical errors
by marking them as they happpen and then display them in a
dialog after we've completely initialized.

I was thinking we could use g_log() with our own special
log domain[s] to mark and report critical and semi-critical
errors, even possibly success messages and then we can
use g_log_set_handler() to collect *all* messages (including
the ones reported by the underlying gtk+ and glib) and
display them in a dialog if any critical errors or
important warnings occurred, Glade-3 critical stuff would be
in red, Glade-3 semi-critical in orange and success messages
would be green, all the other messages would remain the default
black or grey but would still provide context for debugging.
Comment 1 GNOME Infrastructure Team 2018-03-26 14:59:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glade/issues/4.