aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 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-3010-52/+178
|\
| * 0.5.96Charles Kerr2012-03-291-2/+2
| |
| * merge lp:~ken-vandine/dbusmenu/builddir_fixes for distcheck fixesCharles Kerr2012-03-291-0/+1
| |\
| | * Add dbus-menu-clean.xml to EXTRA_DIST and remove previous builddir hack to ↵Ken VanDine2012-03-291-4/+5
| | | | | | | | | | | | fix distcheck
| | * distcheck fixesKen VanDine2012-03-291-4/+4
| |/
| * merge lp:~ted/dbusmenu/instruction-count-testing to support benchmarking ↵Charles Kerr2012-03-295-8/+42
| |\ | | | | | | | | | based on callgrind measurements h/t Chase
| | * Adding in a test to print the number of instructions it takes to export a menuTed Gould2012-03-282-1/+24
| | |
| | * Making the json test signal based instead of timeout basedTed Gould2012-03-282-6/+8
| | |
| | * Insert callgrind annotations into the serverTed Gould2012-03-282-2/+11
| | |
| * | merge lp:~ted/dbusmenu/testing-fixes for improvements to the dbusmenu testsCharles Kerr2012-03-284-24/+77
| |\|
| | * Grabbing the firefox extreme caseTed Gould2012-03-271-0/+43629
| | |\
| | * | Making it so that the JSON handler can handle an array of bytes to specify ↵Ted Gould2012-03-271-3/+21
| | | | | | | | | | | | | | | | images
| | * | Change the dbusmenu-dumper to be realization based instead of timeout basedTed Gould2012-03-271-1/+53
| | | |
| | * | Using the new --wait-for attribute of dbus-test-runnerTed Gould2012-03-272-20/+3
| | | |
| * | | ChrisCoulson's patch to add a lookup hash to avoid the overhead of calling ↵Charles Kerr2012-03-281-7/+55
| |\ \ \ | | | | | | | | | | | | | | | dbusmenu_menuitem_find_id() when possible. See lp bug #801699
| | * | | this is ChrisCoulson's experimental patch to add a lookup hash to avoid the ↵Charles Kerr2012-03-271-7/+55
| | |/ / | | | | | | | | | | | | overhead of calling dbusmenu_menuitem_find_id() when possible.
| * | | fold together client.c's two PROPERTY_CHANGED signal handlersCharles Kerr2012-03-281-12/+2
| |\ \ \
| | * | | fold client's two DBUSMENU_MENUITEM_SIGNAL_PROPERTY_CHANGED signal handlers ↵Charles Kerr2012-03-271-12/+2
| | |/ / | | | | | | | | | | | | together for clarity
* | | | 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
|/ / /
* | | Don't sent event replies that aren't requestedTed Gould2012-03-281-1/+3
|\ \ \
| * | | server: don't send replies for events that don't request repliesRyan Lortie2012-03-271-1/+3
| |/ /
* | | merge lp:~ted/dbusmenu/firefox-extreme-case for tests/test-json-02.jsonCharles Kerr2012-03-271-0/+43629
|\ \ \ | |/ / |/| / | |/
| * Adding a Firefox extreme menu case for testingTed Gould2012-03-271-0/+43629
|/
* 0.5.95Ted Gould2012-03-211-3/+3
|
* merge lp:~charlesk/dbusmenu/lp-953509 to fix a crash in dbusmenu-gtk's ↵Charles Kerr2012-03-212-59/+11
|\ | | | | | | handling of menu icon theme changes
| * Don't listen for "changed" events from the screen's default GtkIconTheme. ↵Charles Kerr2012-03-211-51/+0
| | | | | | | | | | | | | | | | | | Fixes lp bug #953509 The crash in #953509 was being caused by the last two lines of theme_changed_cb() (a) leaving a dangling handler id in priv.theme_changed_sig, and (b) not remembering the handler id of its own signal connection. However after testing I don't see any reason to keep any of the theme handling code at all. "But wait," you say. "How will our menu icons follow the theme changes?" It works in practice anyway because we always listen for property changes to our reference GtkImage, **and** we listen for property changes to its GtkImageMenuItem parent so that if the GtkImageMenuItem changes GtkImages we can stop listening to the old one and start listening to the new one.
| * merge lp:~ted/dbusmenu/regex_merge to fix a warning that comes up a lot with ↵Charles Kerr2012-03-201-8/+11
|/| | | | | | | unity-panel-service about not having a label.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 06:07:51 +0000