ayatana-indicator-datetime/src, branch 0.3.91

Change GSetting bindings to be read only

2012-03-08T22:40:31+00:00

Establish read-only bindings to GSettings from the indicator

2012-03-07T20:49:58+00:00

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.

more GVariantBuilder vs. G_VARIANT_TYPE_ARRAY fixes

2012-03-07T20:36:07+00:00

merge lp:~charlesk/indicator-datetime/fix-943747 to silence the Coverity warning reported in bug #943747

2012-03-05T21:52:28+00:00

In Bug #943747, Coverity reported that use of sscanf() needed to be inspected by a human to verify there aren't buffer overruns. This commit adds /* coverity[secure_coding] */ to the lines before the calls to tell Coverity that they've been checked.

2012-03-04T00:46:53+00:00

remove unused code in populate_appointment_instances().

2012-03-03T19:45:25+00:00

It looks like the local variables 'datetime', 'appointment_zone', and 'current_zone' were used in earlier revisions of the code, but this was removed in . They're currently leftover code, and removing them should fix Bug #943746.

merging lp:~charlesk/indicator-datetime/fix-833337 and lp:~charlesk/indicator-datetime/fix-leaks

2012-03-03T16:23:06+00:00

simplify the code by removing special handling for geo_location and current_location, and adding them to the same 'locations' list that we use when pruning duplicates from the user-specified list of locations

2012-03-02T21:02:31+00:00

use g_return_if_fail() instead of g_assert() in the new code

2012-03-02T20:13:18+00:00

remove duplicate timezone entries

2012-03-02T20:12:20+00:00