summaryrefslogtreecommitdiff
path: root/gio/gsettings.h
Commit message (Collapse)AuthorAgeFilesLines
* Annotate API introduced for 2.32 with GLIB_AVAILABLE_IN_2_32Colin Walters2012-05-261-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=676816
* add a way to create a GAction from GSettingsRyan Lortie2012-01-191-0/+3
| | | | | | | | g_settings_create_action() will create a GAction for the named key, allowing it to be added to the action group of the application (so that the setting can be directly manipulated from menus, for example). https://bugzilla.gnome.org/show_bug.cgi?id=668279
* Drop last uses of @returns:Ryan Lortie2011-11-211-4/+7
|
* Clarify docs/params for 'schema' vs 'schema id'Ryan Lortie2011-11-171-4/+4
| | | | | Clean up our parameter naming and documentation to draw a clearer line between a schema and its identifier.
* Add g_settings_new_full() taking GSettingsSchemaRyan Lortie2011-11-171-0/+4
|
* Add 'uint' convenience functions for GSettingsRyan Lortie2011-03-311-0/+5
| | | | | | | | Without getting into a debate about the reasons why you may or may not want to use unsigned integers, it's sufficient to note that people have been using them and requesting this functionality. Bug #641755.
* Docs: Changed can not to cannot.Murray Cumming2011-03-241-1/+1
|
* Add and update GI annotations in 'Settings'Pavel Holejsovsky2011-01-071-2/+3
| | | | 'Settings' GIO group contains GSettings and GSettingsBackend.
* GSettings: add g_settings_range_check() APIRyan Lortie2010-10-041-0/+3
| | | | Checks if a given value is within the correct range for a key.
* Bug 631263 - GSettings needs range/choice APIsRyan Lortie2010-10-041-0/+2
| | | | | | | Add g_settings_get_range() to describe the possible values that may be provided to g_settings_set_value() without causing an error. Add a test case.
* Clean up g_settings_list_schemas()Ryan Lortie2010-10-021-0/+1
| | | | | | | | | | | | In its previous form, g_settings_list_schemas() was not useful as a tool to prevent aborts due to using g_settings_new() with an invalid schema name. This is because g_settings_list_scheams() also listed relocatable schemas, and calling g_settings_new() for those would abort just the same as if you called it for a non-existent schema. Modify g_settings_list_schemas() so that it only returns schemas for which it is safe to call g_settings_new(). Add another call for sake of completeness: g_settings_list_relocatable_schemas().
* GSettings: reverse accidental addition to .h fileRyan Lortie2010-09-141-3/+0
| | | | | A couple of extra function prototypes snuck into commit 77e3badcf3f15c7ac235904160d775febfcebcb5. Take those out.
* split GSettings.list_items => list_{children,keys}Ryan Lortie2010-09-091-1/+5
| | | | This is an incompatible public API/ABI change.
* GSettings: add G_SETTINGS_BIND_INVERT_BOOLEAN flagRyan Lortie2010-08-031-1/+5
| | | | | | | | | | When binding a boolean setting to a boolean property, invert the values. This avoids the requirement for writing a pair of mapping functions for this extremely common case. Add a test. https://bugzilla.gnome.org/show_bug.cgi?id=625833
* GSettings: add g_settings_reset()Ryan Lortie2010-07-221-0/+2
| | | | Resets a key to its default value.
* gio/ docs fixupRyan Lortie2010-07-121-1/+1
|
* Bug 622124 - implement flags for GSettingsRyan Lortie2010-07-011-0/+5
| | | | | | | | Add a <flags> tag to the schema file format and a flags='' attribute to go along with. Add some extra test cases for those. Add new g_settings_{get,set}_flags() calls and support binding to GParamSpecFlags properties. Add test cases.
* g_settings_list_keys() -> _list_items()Ryan Lortie2010-06-301-1/+1
| | | | This function returns children as well.
* Bug 622127 - GSettings extended key validationRyan Lortie2010-06-281-0/+27
| | | | | First shot at attempting to implement this in a reasonable way. See the bug for more information about why this is needed.
* Tweak GSettings key/schema listing APIsRyan Lortie2010-06-241-2/+2
|
* GSettings: add g_settings_list_keys()Ryan Lortie2010-06-241-0/+1
| | | | Second half of bug #622554.
* Add g_settings_schema_existsRyan Lortie2010-06-241-0/+1
| | | | Solves half of #622554.
* Make g_settings_sync() a proper prototype.Ryan Lortie2010-06-171-1/+1
|
* Bug 621266 - GSettings "context" clarificationRyan Lortie2010-06-171-6/+5
| | | | | Remove the concept of "context" in favour of dealing with GSettingsBackend directly.
* move GSettings(Backend) to giotypes.hRyan Lortie2010-06-161-2/+1
|
* GSettings: major refactor. Add enums, range.Ryan Lortie2010-06-161-1/+5
|
* Add g_settings_sync() and use itRyan Lortie2010-06-101-0/+1
|
* Add single-include guards to new headersMatthias Clasen2010-06-061-0/+4
| | | | | As pointed out by Christian Persch in bug 620173, all the new gdbus and gsettings headers were missing these.
* Remove length parameter for g_settings_[gs]et_strvMilan Bouchet-Valat2010-06-021-4/+2
| | | | | | | | Length of the array is redundant since it's NULL-terminated. This is not consistent with many GLib and GTK+ functions, and adds complexity with no real gain, while these convenience functions should be kept simple. Closes bug #620312
* Handle non-readable/-writable properties when bindingMatthias Clasen2010-04-211-2/+4
| | | | And document readability/writability requirements for binding flags.
* GSettings: bind to writablity of a keyRyan Lortie2010-04-201-0/+5
|
* Document G_SETTINGS_BIND_GET_NO_CHANGESMatthias Clasen2010-04-171-3/+5
|
* merge GSettingsRyan Lortie2010-04-161-0/+203
View Lorry Controller Status