aboutsummaryrefslogtreecommitdiff
path: root/libdbusmenu-glib/client.c
Commit message (Collapse)AuthorAgeFilesLines
* Managing the lifecycle of the menu item more directly and making sure to ↵Ted Gould2009-10-021-1/+37
|\ | | | | | | remove them from the menu when they're not children of it anymore.
| * Adding in printing for type handlers and getting root.Ted Gould2009-10-011-0/+8
| |
| * Axing long propsTed Gould2009-10-011-1/+1
| |
| * Another, typoTed Gould2009-10-011-1/+1
| |
| * Creating some massive debugging on basically every event from these folks. ↵Ted Gould2009-10-011-1/+29
| | | | | | | | We want to know it all.
* | We weren't checking to see if error wasn't null, and therefore we reacted on ↵Ted Gould2009-10-021-0/+8
|/ | | | a bad hashtable which caused a crash.
* Updating prototype for signalTed Gould2009-09-211-1/+1
|
* Getting the revision data off of the root node there.Ted Gould2009-09-211-1/+30
|
* Save the 'current' version and track whether we need to request an update.Ted Gould2009-09-211-3/+7
|
* Changing from a boolean to tracking rev numbers in the private structure.Ted Gould2009-09-211-13/+17
|
* Adding in a second checking of the layout if we look for it while we're ↵Ted Gould2009-09-171-8/+9
| | | | still requesting it. We're not sure if this creates an issue between the syncing of the two objects.
* Commenting out the blocking on root waiting for an update.Ted Gould2009-09-111-0/+6
|
* Making sure that type is not NULL. Comment from Neil.Ted Gould2009-08-271-0/+1
|
* Check the return of g_new0 for NULL. Comment by Neil.Ted Gould2009-08-271-5/+9
|
* Comment for Neil. Checking data.Ted Gould2009-08-271-0/+2
|
* Adding in a default type handler, incase it's configured, but not set by ↵Ted Gould2009-08-261-0/+2
| | | | clients.
* Ah, bother. Check NULL. Brain fart.Ted Gould2009-08-251-1/+1
|
* It turns out that when you define functions in a header file, they don't ↵Ted Gould2009-08-251-0/+43
| | | | just write themselves from your thoughts. Who's supposed to tell me these things? Anyway, now we have a way to register type handlers, like the header file said we should.
* Switching the prototype for type handlers so that it passes the client as well.Ted Gould2009-08-251-1/+1
|
* Signaling the realized event after it has all it's parameters.Ted Gould2009-08-251-0/+2
|
* Making things a little more type safe. Only one evil cast.Ted Gould2009-08-201-13/+21
|
* Makin' it so that if we have a type handler we use that, otherwise we pass ↵Ted Gould2009-08-201-2/+20
| | | | things up. Also making it so that type handlers can report an error.
* Switching the new signal to be after the properties are gotten and adding a ↵Ted Gould2009-08-201-2/+32
| | | | hashtable for type handlers.
* Heh, turns out we need to actually signal people across DBus or nothing ↵Ted Gould2009-07-201-0/+21
| | | | works. Who'd a thought.
* Add the property of the menuitems to check to see if they're the root node ↵Ted Gould2009-06-261-0/+3
| | | | or not. Also set that when the layout is being parsed.
* Switching the loss of the proxies to be warnings instead of errors as we can ↵Ted Gould2009-06-261-2/+2
| | | | recover from it and handle it gracefully if we need to.
* Flipping arround the original update of the layout to be after building the ↵Ted Gould2009-06-261-3/+3
| | | | proxies, not something driven by new. Also ensuring that the callback pointer is reset when we're in it so that it doesn't get called recursively.
* Signaling on root changes.Ted Gould2009-06-231-1/+8
|
* Signaling the new menuitem.Ted Gould2009-06-231-4/+5
|
* Adding two new signals to the client. 'root-changed' and 'new-menuitem' to ↵Ted Gould2009-06-231-0/+35
| | | | make it so that this can go up the stack easier.
* Updating to the latest from gtkmenuTed Gould2009-06-181-1/+2
|\
| * Updates from trunk with the properites branch.Ted Gould2009-06-051-1/+2
| |\
| | * Making the ID update function rebuild all of the properties. Result of a ↵Ted Gould2009-06-051-1/+2
| | | | | | | | | | | | code review comment by Cody Russell.
* | | Making it so that if we clear the menu structure by destroying the proxies ↵Ted Gould2009-06-181-0/+1
| | | | | | | | | | | | we also signal that to the callers.
* | | Handle the server removing itself from the bus and putting us into a dark ↵Ted Gould2009-06-181-2/+25
| | | | | | | | | | | | world waiting for it to rejoin the world.
* | | If we can't get a proxy on the stuff that we want, we're going to set up a ↵Ted Gould2009-06-181-0/+73
| | | | | | | | | | | | DBus one and just wait for it to show up. When it showes up, then we'll pounce
* | | Handling the concept of not having a property proxy.Ted Gould2009-06-181-1/+10
|/ /
* | Unref'ing root when we disposeTed Gould2009-05-251-0/+5
| |
* | Playing with debug stuffTed Gould2009-05-251-0/+4
|/
* Disabling a large number of debug messages. Most aren't needed anymore.Ted Gould2009-05-191-5/+5
|
* Recycle the server's marshaller and register it with DBus as we don't have ↵Ted Gould2009-05-191-0/+2
| | | | one for IdPropUpdate. The server and the client can use the same one.
* Now we're calling the get_properties function on every menuitem that we ↵Ted Gould2009-05-191-4/+28
| | | | build. Fun.
* Okay, throwing the signals down to the menuitemsTed Gould2009-05-131-0/+16
|
* Connecting to the other signals coming from the serverTed Gould2009-05-131-0/+22
|
* Checking parameter. Found by Cody Russell.Ted Gould2009-05-121-0/+2
|
* Public API functions documentationTed Gould2009-05-121-1/+28
|
* Add in the LGPL 2.1/3 text to the tops of the files.Ted Gould2009-05-121-0/+28
|
* Taking the children, and trying to reuse them if possible. Sometimes that ↵Ted Gould2009-05-111-1/+21
| | | | doesn't work out and we have to put one down. It's always sad to loose one, but sometimes it has to happen.
* More debuggingTed Gould2009-05-081-1/+6
|
* Debugging messages and switching the ID gathering function around.Ted Gould2009-05-061-4/+12
|