aboutsummaryrefslogtreecommitdiff
path: root/libdbusmenu-glib/client.c
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Adding in a signal for the layout being updatedTed Gould2009-05-051-0/+25
|
* Adding in signals to get the update from the server updating the layout. ↵Ted Gould2009-05-051-0/+17
| | | | And parsing it.
* Adding the layout into the error message.Ted Gould2009-05-041-1/+1
|
* Don't init the value, as DBus will do that.Ted Gould2009-05-041-2/+0
|
* Making sure to clear the call on error too.Ted Gould2009-04-281-0/+1
|
* Fix property names.Ted Gould2009-04-281-3/+6
|
* Okay, it think we're syncing the two XML hierarchies. Whew.Ted Gould2009-04-271-3/+49
|
* Getting up to the XML level. Whoo, up the protocol stack we go.Ted Gould2009-04-271-0/+26
|
* Handling all the DBus-isms of getting the property, now passing up the stack ↵Ted Gould2009-04-271-10/+44
| | | | to a parse function which will actually take care of the data.
* Creating a lifecycle for our dbus proxies. We created them, so we must ↵Ted Gould2009-04-271-1/+63
| | | | destroy them as well.
* Addign in the get and set properties.Ted Gould2009-04-271-1/+38
|
* Adding in properties.Ted Gould2009-04-271-0/+43
|
* Starting to flesh out the client a little bitTed Gould2009-04-201-0/+63
|
* Changing the type name to make more senseTed Gould2009-04-161-1/+1
|
* Linking in the dbus prototypes generated by the dbus tools.Ted Gould2009-04-151-0/+1
|
* Adding basic client and server objects.Ted Gould2009-04-151-0/+53