aboutsummaryrefslogtreecommitdiff
path: root/libdbusmenu-glib
Commit message (Collapse)AuthorAgeFilesLines
* merge lp:~charlesk/dbusmenu/constify-dbusmenu-menuitem-gettersCharles Kerr2012-08-212-13/+13
|\
| * constify the dbusmenu_menuitem_get*() functionsCharles Kerr2012-04-252-13/+13
| |
* | don't include build-time filenames in comments of the enum header filesunknown2012-05-241-1/+1
| | | | | | | | | | | | | | | | | | If we do, the header files may be different on each build. This is especially harmful when building multiple times for multiple architectures and expecting the files to be identical. See: http://bugs.debian.org/674200
* | Evan Nemerson's patch to make the Vala bindings use pkg-config names, rather ↵Charles Kerr2012-04-261-3/+3
|\ \ | |/ |/| | | than GIR names, so that valac can automatically pick up the relevant libraries and flags.
| * apply Evan Nemerson's patch to make the Vala binidngs use pkg-config names, ↵Charles Kerr2012-04-111-3/+3
| | | | | | | | not GIR names, so that valac can automatically pick up the relevant libraries and flags.
* | fix leaky DbusmenuServer.priv.dbusobjectCharles Kerr2012-04-141-0/+5
|/
* In menuitem_signals_remove(), disconnect the ↵Charles Kerr2012-04-101-0/+1
| | | | | | | DBUSMENU_MENUITEM_SIGNAL_SHOW_TO_USER event that we connected to in menuitem_signals_create(). It looks like this non-disconnected signal goes all the way back to July 2010 <http://bazaar.launchpad.net/~dbusmenu-team/dbusmenu/trunk.0.6/revision/139#libdbusmenu-glib/server.c> so I'd like ted's eyes on this to confirm there's not some nuance that I'm missing...
* merge lp:~ted/dbusmenu/about-to-show-tuple to fix about-to-show grouping.Charles Kerr2012-04-091-3/+5
|\
| * Apparently this type is wrong, if only this language supported some way to ↵Ted Gould2012-04-091-1/+1
| | | | | | | | communicate to programmers the types that variables were. Oh, we can dream.
| * Pull the items out of the tupleTed Gould2012-04-091-2/+4
| |
* | make event_data_find() and session_bus_cb() private instead of publicCharles Kerr2012-04-051-2/+2
| |
* | Make sure that if the callback is NULL we're not trying to get a callbackTed Gould2012-04-041-1/+5
| |
* | Protect from the cases where we might get NULL in the data segmentTed Gould2012-04-041-1/+8
|/
* Merge lp:~ted/dbusmenu/event-grouping to reduce the number of dbus messages ↵Charles Kerr2012-04-044-54/+666
|\ | | | | | | | | | | | | that hud-service sends. This change takes all of the events on a client and puts them into single dbus messages to be sent to the server. It also does the same thing for about-to-show messages. Both sets of messages are reserialized on either side to make callers unable to notice the difference.
| * Fixing a cut-and-paste commentTed Gould2012-04-031-1/+1
| |
| * Switching to GQueueTed Gould2012-04-031-28/+36
| |
| * Fill out the group callback to update if we need itTed Gould2012-04-031-0/+30
| |
| * Fleshing out the idle handler for about to showTed Gould2012-04-031-0/+74
| |
| * Setup our idle if we're grouping the eventsTed Gould2012-04-031-8/+37
| |
| * Set up the about-to-show task tracking variablesTed Gould2012-04-031-1/+28
| |
| * Pulling out parts of about to show so that we have a core function thereTed Gould2012-04-031-12/+21
| |
| * Set and get the event grouping and notify if we change itTed Gould2012-04-031-0/+13
| |
| * Add a property to whether we should group events or notTed Gould2012-04-032-1/+12
| |
| * Making sure to clear the idle so we queue againTed Gould2012-03-301-0/+1
| |
| * Unpacking the tupleTed Gould2012-03-301-1/+3
| |
| * Making sure to init our errorTed Gould2012-03-301-1/+1
| |
| * Making sure the variant is appropriately wrappedTed Gould2012-03-301-2/+3
| |
| * If we're going to unref we should set to NULL to catch potential errorsTed Gould2012-03-301-0/+3
| |
| * Checking the version of the server to see if we can group the propertiesTed Gould2012-03-301-0/+32
| |
| * Okay, making all the callbacks real and returning appropriate errorsTed Gould2012-03-301-1/+53
| |
| * Make the getting of properties debug messages as they can happen in normal usageTed Gould2012-03-301-2/+2
| |
| * Putting a warning in dispose for something we shouldn't have to doTed Gould2012-03-301-0/+1
| |
| * Setting up our callback functionTed Gould2012-03-301-1/+14
| |
| * Flesh out the idle callback so we're not actually sending a message on DBus! Ted Gould2012-03-301-1/+55
| |
| * Switching to a linked list of event_data structures getting passed to the ↵Ted Gould2012-03-301-33/+27
| | | | | | | | idle function
| * Splitting out the ending of the event_data objectTed Gould2012-03-301-7/+17
| |
| * Handle the case of sending to the idle.Ted Gould2012-03-301-0/+28
| |
| * Start by adding the data we're going to need to our private structureTed Gould2012-03-301-0/+17
| |
| * Move the actual about-to-show call into the idle incase we get a ton of them ↵Ted Gould2012-03-301-2/+14
| | | | | | | | (I'm looking at you HUD)
| * Fleshing out the about-to-show group handlerTed Gould2012-03-301-1/+55
| |
| * Make it so the memory handling of the event_core function is more ↵Ted Gould2012-03-301-4/+5
| | | | | | | | predictable and correct.
| * Fleshing out the event group functionTed Gould2012-03-301-1/+48
| |
| * Adding a way to give a partial error of IDs not being foundTed Gould2012-03-301-0/+12
| |
| * Pulling the core event handling into its own functionTed Gould2012-03-301-12/+23
| |
| * Merging trunkTed Gould2012-03-302-7/+56
| |\
| * | Put in functions to handle the new group functionsTed Gould2012-03-301-0/+32
| | |
| * | Adding two grouping functions for events and about to showTed Gould2012-03-301-0/+34
| | |
| * | Bumping the version of the wire protocolTed Gould2012-03-301-1/+1
| | |
* | | Merge lp:~allanlesage/dbusmenu/TDD to add gcov targets to autotools build ↵Charles Kerr2012-04-031-1/+8
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | for code-coverage reporting. For more information, see this blog post: http://qualityhour.wordpress.com/2012/01/29/test-coverage-tutorial-for-cc-autotools-projects/ . To compile with coverage tooling, ./autogen.sh --enable-gcov, then make coverage-html . Note that you'll need lcov to autoconf. Also note that you'll get an error on make if you have no tests, as there are no coverage artifacts to generate the html report. For review, please pay special attention to flags added in the project's makefiles.
| * | Added gcov coverage tooling.Allan LeSage2012-03-271-1/+8
| | |