Re: [evolution-patches] 72088, force loading some types in calendar a11y code

[Rodrigo Moya <rodrigo novell com>]

On Wed, 2005-02-02 at 13:27 +0800, Harry Lu wrote:
> JP and Rodrigo,
>     When I run CVS head version of evolution, I found some calendar a11y 
> functions don't work. There are also some warnings in the output:
> (evolution-2.2:31757): GLib-GObject-WARNING **: gsignal.c:1019: unable 
> to lookup signal "event" of unloaded type `EText'
> (evolution-2.2:31757): GLib-GObject-CRITICAL **: file gsignal.c: line 
> 822 (g_signal_add_emission_hook): assertion `signal_id > 0' failed
> (evolution-2.2:31757): GLib-GObject-WARNING **: gsignal.c:1019: unable 
> to lookup signal "event" of unloaded type `GnomeCanvasPixbuf'
> (evolution-2.2:31757): GLib-GObject-CRITICAL **: file gsignal.c: line 
> 822 (g_signal_add_emission_hook): assertion `signal_id > 0' failed
> (evolution-2.2:31757): GLib-GObject-WARNING **: gsignal.c:1019: unable 
> to lookup signal "event" of unloaded type `EDayViewMainItem'
> (evolution-2.2:31757): GLib-GObject-CRITICAL **: file gsignal.c: line 
> 822 (g_signal_add_emission_hook): assertion `signal_id > 0' failed
> (evolution-2.2:31757): GLib-GObject-WARNING **: gsignal.c:1019: unable 
> to lookup signal "event" of unloaded type `EWeekViewMainItem'
> (evolution-1.2:31757): GLib-GObject-CRITICAL **: file gsignal.c: line 
> 822 (g_signal_add_emission_hook): assertion `signal_id > 0' failed
> 
>     As I checked, this might due to the changes in gobject. Some object 
> types are not loaded when we use them.
>     Here is a patch to force loading some types. Please review it.
>
just found this mail on my inbox, and not sure if it's been approved or
not. If not, it looks ok to me. Although I haven't seen those warnings
at all myself.
-- 
Rodrigo Moya <rodrigo novell com>