ayatana-indicator-datetime/src/indicator-datetime.c, branch main Ayatana Indicator Date & Time Applet https://openid.arctica-project.org/ayatana-indicator-datetime/atom?h=main 2013-06-14T21:01:43+00:00 remove the old indicator & service code 2013-06-14T21:01:43+00:00 Charles Kerr charles.kerr@canonical.com 2013-06-14T21:01:43+00:00 urn:sha1:e392dd10a5dde1a0333fdeb963ecb1efecc8b19a this is an assertion, so use g_assert() 2013-05-02T00:44:45+00:00 Charles Kerr charles.kerr@canonical.com 2013-05-02T00:44:45+00:00 urn:sha1:e03ef8e4ac74e87cefaff1ef792d8a5bff54c926 since we're just testing to see if the calendar's been created yet, test for NULL instead of using IDO_IS_CALENDAR_MENU_ITEM() 2013-05-02T00:42:59+00:00 Charles Kerr charles.kerr@canonical.com 2013-05-02T00:42:59+00:00 urn:sha1:13b5da4c6715e536851dc974fc44ecd235885175 fix for the datetime g_critical reported by desrt 2013-05-01T23:39:52+00:00 Charles Kerr charles.kerr@canonical.com 2013-05-01T23:39:52+00:00 urn:sha1:c5e72bbaf1744a6693e6a69cfe67c2aa914d3843 minor tyop fix: s/notfy/notify/ 2013-05-01T23:26:37+00:00 Charles Kerr charles.kerr@canonical.com 2013-05-01T23:26:37+00:00 urn:sha1:8ef94b74f304b3d039a37b3c0a68c8e51d88cf5f fix r189 oops. This code would be cleaner if handled upstream in IDO... filed side ticket #1061364 for that side issue 2012-10-04T04:20:11+00:00 Charles Kerr charles.kerr@canonical.com 2012-10-04T04:20:11+00:00 urn:sha1:b35e40efc47e8e3bc3e3683e61f2d078f6ec8628 When showing/hiding the menu, don't change the calendar date if it's already what we want. This way we avoid unnecessary appointment rebuilds in the service. 2012-10-04T03:27:33+00:00 Charles Kerr charles.kerr@canonical.com 2012-10-04T03:27:33+00:00 urn:sha1:6db1219ef000df92d5389922123fe85170fa9350 update all of the indicator's labels when the menu's visibility changes to true 2012-09-20T01:09:14+00:00 Charles Kerr charles.kerr@canonical.com 2012-09-20T01:09:14+00:00 urn:sha1:409f65de28ab57035c7d6945060573a32a69b6cc require gtk3 2012-05-07T23:48:29+00:00 Charles Kerr charles.kerr@canonical.com 2012-05-07T23:48:29+00:00 urn:sha1:8c6f958633aca2dcd9999782939eafc7a32d7cb0 Establish read-only bindings to GSettings from the indicator 2012-03-07T20:49:58+00:00 Ryan Lortie desrt@desrt.ca 2012-03-07T20:49:58+00:00 urn:sha1:562575c97ba29a47cd64c85c20725267b79d593b The bindings to GSettings are established in the GTypeInstance _init function of the indicator. During this time, the property notify queue is frozen. After the construction completes, the queue thaws and the rush of property change notifications causes GSettings writes to occur. We can fix this by switching to using readonly bindings.