Right now, if both KeyList and KeyListEntry contain a schema element,
the (global) one of the list wins. This makes it rather cumbersome
to mix keys of different schemas in a single list, as rather than
using a default schema and specifying a different one where necessary,
every key needs its own schema element.
A brief IRC discussion suggests that the current precedence didn't
trigger any particular issues before, and neither should changing
it - so do this to support above case.
https://bugzilla.gnome.org/show_bug.cgi?id=653685
default_app_changed() contains a typo: we need to set the https
handler app when the user changes the http app chooser, not the
(non-existent) https app chooser.
A menu popup was the best thing we could find after discussing it on
If anybody has any better ideas then please shout / send patches.
To show the menu, press the context menu key on the keyboard.
GTK+ 3.0 introduced gtk_tree_model_iter_previous() so we no longer need to
keep this helper function.
Also, simplify the use of GtkTreeIters by allocating them on the stack.
https://bugzilla.gnome.org/show_bug.cgi?id=652374
Setting updating_settings in update_layouts_list() and checking for it in the
gsettings 'changed' signal handler doesn't prevent a loop because the signal
handler is only called after update_layouts_list() returns and thus
updating_settings is already FALSE at that point.
By using the 'drag-end' signal instead of 'row-inserted', etc. we continue to
support DnD re-ordering of layouts while avoiding the loop from
xkb_layouts_fill_selected_tree() deleting and inserting rows into the model.
https://bugzilla.gnome.org/show_bug.cgi?id=652361
Setting the date manually should be disabled when using NTP, but
the "Network Time" setting is not taken into account when updating
sensitivities after permission changes. As a result, the date is
always editable after unlocking the panel - to fix, take the NTP
setting into account on permission changes.
https://bugzilla.gnome.org/show_bug.cgi?id=652240
The libcolord async API used to use a thread to get the properties for the
device and profiles in the background.
This was racy as hell, and was not good API design. Connect to each device and
profiles explicitly before we access the properties.
