On Tue, 2014-06-17 at 14:30 +0005, Khurshid Alam wrote: > What do you mean by that? On Ubuntu, panel was always built against > respective EDS available. Here is the complete scenario: > > Gnome-Panel EDS Ubuntu Status > (EDS-Integration in clock) > --------------------------------------------------------------------- > 3.6 3.6 12.10 > Working #patch provided here > > 3.6 3.8 13.10 > Not Working > > 3.8 3.8 13.10 > Not Working > > 3.6 3.10 14.04 Not > Working > > 3.8 3.10 14.04 Not > Working
Hi, it seems to me like it wasn't always build against the right eds, or your runtime doesn't have the right eds? Unlike, right? Anyway, let him know to check applets/clock/calendar-sources.c:calendar_sources_init(), whether the call of e_source_registry_new_sync() succeeded or not. Then he can check what the calendar_sources_get_appointment_clients() returns - it should return nonempty list of ESource-s corresponding to the type (Events or Todos). The other interesting part is at applets/clock/calendar-client.c, namely the cal_opened_cb(), where is decided whether the calendar was properly opened or not. When it succeeds, then either calendar_client_update_appointments() or calendar_client_update_tasks() is called at the end of that function. I'd debug in these functions, to see whether it does what it should do. I see in the code (I only briefly looked into it), that it is almost up to date, it only uses deprecated ECal structures, while current supported API is ECalClient. It's possible that the deprecated structures misbehave in some way. The code might be rewritten to use ECalClient ideally, because the deprecated structures are deprecated for years, thus they will be gone sooner or later. Hope it helps, Milan _______________________________________________ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers