- Jul 29, 2012
-
-
Allison Karlitskaya authored
Also add the equivalent vfunc to the backend. https://bugzilla.gnome.org/show_bug.cgi?id=668233
-
Allison Karlitskaya authored
So far only supporting getting key summary/description. https://bugzilla.gnome.org/show_bug.cgi?id=668232
-
Allison Karlitskaya authored
-
Allison Karlitskaya authored
Implement it for GMemorySettingsBackend.
-
Allison Karlitskaya authored
This was only used by the (now removed) delayed settings backend.
-
Allison Karlitskaya authored
This was only used by the (now removed) delayed settings backend.
-
Allison Karlitskaya authored
This breaks the tests, but will be added back in another form soon.
-
Allison Karlitskaya authored
This vfunc gets a delayed settings backend appropriate for use with this type of GSettingsBackend.
-
Allison Karlitskaya authored
Remove this API from GDelayedSettingsBackend.
-
Allison Karlitskaya authored
Now that signals connected to GObjects are threadsafe, it is far easier for us to do it this way.
-
Allison Karlitskaya authored
This is an API break. It modifies the writable-change-event signal and vfunc to be more like the change-event signal. I don't think anyone is implementing or connected to this. Also, remove a lie from the documentation for the same signal.
-
Allison Karlitskaya authored
Add GSettingsBackend API to allow any backend to have a 'has-unapplied' property. Remove the 'owner' hackery that was used for notifying of changes to 'has-unapplied' and just use normal GObject notify (and wire into that from the frontend).
-
Allison Karlitskaya authored
The main context dispatching logic substantially complicates the backend and is only needed for the GSettings frontend. Move it there instead.
-
Allison Karlitskaya authored
Drop the 'vtable' business and switch to a single callback that takes a new GSettingsEvent structure. This patch temporarily regresses delayed settings: if a key set within a delayed settings backend becomes non-writable, it is no longer removed from the changeset.
-
- Jul 25, 2012
-
-
Мирослав Николић authored
-
- Jul 24, 2012
-
-
Yaron Shahrabani authored
-
- Jul 23, 2012
-
-
-
Kjartan Maraas authored
-
- Jul 20, 2012
-
-
The old (length) annotation actually wasn't being read. Changing it to an array was telling g-i that it was an array of utf8, which is clearly not true. We *could* add (element-type guint8), but that would change it to a byte array, as opposed to the original utf8 version. Just removing the annotation should bring us back to where we were, which was fine. https://bugzilla.gnome.org/show_bug.cgi?id=680310
-
- Jul 19, 2012
-
-
Chun-wei Fan authored
gcontenttype.c was split into gcontenttype.c and gcontenttype-win32.c in commit 32192ee9 ("Split gcontenttype.c"), so we don't want to include gcontenttype.c in the Visual C++ build as it is no longer a source file meant for Windows. Thanks to Thomas H.P. Anderson for pointing this out.
-
Matthias Clasen authored
Bug 680148 claims that PR_SET_NAME may not be defined when using an old kernel. Deal with it.
-
Matthias Clasen authored
Bug 680074 shows that we may end up in situations where only some of the xlocale functions we need are available. Rather than trying to find the minimal set of required functions for each use, define a global USE_XLOCALE and only use any xlocale functions if we have a full set.
-
Matthias Clasen authored
Somehow a few ^M sneaked in here.
-
- Jul 18, 2012
-
-
Dan Winship authored
Fix a crash when a child source is destroyed before its parent. Also, add a test case for this and the previous fix.
-
Dan Winship authored
Child sources are supposed to be blocked when their parents are, so when adding a source to a blocked source, block the child too. Fixes a warning when unblocking the parent.
-
- Jul 17, 2012
-
-
Dan Winship authored
Add a test that the decompressor input streams handle truncated data correctly. (They do; I wrote the test thinking there was a bug there, but there isn't.) Also, rename the "corruption" tests to "roundtrip", since "corruption" makes it sound like we're testing how the converters deal with corrupted data, as opposed to merely testing that they don't corrupt data themselves. And fix the bug reference.
-
Dan Winship authored
Rather than implementing GCancellableSource by polling on its fd, implement it by just waking its GMainContext up from the "cancelled" signal handler, thereby helping to reduce file descriptor usage. Suggested by Ryan Lortie. https://bugzilla.gnome.org/show_bug.cgi?id=680121
-
Matthias Clasen authored
-
Matthias Clasen authored
-
* GCancellable can be "cancelled" more than once if g_cancellable_reset() is called. * Don't assume that because the "cancelled" signal fired it won't fire again. https://bugzilla.gnome.org/show_bug.cgi?id=680111
-
-
Dan Winship authored
g_async_initable_real_init_finish() was previously handling all GSimpleAsyncResults, even if they weren't created by g_async_initable_real_init_async(), and libnm-glib accidentally relied on that behavior. So remove the g_simple_async_result_is_valid() check.
-
- Jul 16, 2012
-
-
Krzesimir Nowak authored
This are mistaken by g-ir-scanner as GVariantType's methods, because they take a GVariantType* as a first parameter. https://bugzilla.gnome.org/show_bug.cgi?id=679968
-
Daniel Mustieles García authored
-
Marc-André Lureau authored
On Windows, GetEnvironmentVariable() returns 0 for empty variables. Checking GetLastError() == ERROR_ENVVAR_NOT_FOUND helps make a difference between a variable that does not exist or an empty one which should return "". https://bugzilla.gnome.org/show_bug.cgi?id=679617
-
Marc-André Lureau authored
The current code create the strv array incorrectly, it is too big and leaves invalid holes. This may result in crashes when freeing the returned value. https://bugzilla.gnome.org/show_bug.cgi?id=679617
-
Matthias Clasen authored
-
Matthias Clasen authored
-
- Jul 15, 2012
-
-
Ihar Hrachyshka authored
-
- Jul 14, 2012
-
-
Piotr Drąg authored
-