aboutsummaryrefslogtreecommitdiff
path: root/libdbusmenu-glib
Commit message (Collapse)AuthorAgeFilesLines
...
| * Truncating property values if they're too long.Ted Gould2009-10-011-1/+1
| |
| * Being more explicity about the position that things are placed in.Ted Gould2009-10-011-4/+4
| |
| * Got our cast on backwards.Ted 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-012-1/+53
| | | | | | | | 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
|
* Adding the revision to the signal in the dbus spec.Ted Gould2009-09-211-0/+1
|
* 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
|
* Putting the revision number into the XML sent across the bus.Ted Gould2009-09-213-7/+9
|
* Cleanup changes from last commit.Ted Gould2009-09-212-1/+3
|
* Updating the signal to send a revision numberTed Gould2009-09-211-6/+15
|
* 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.
* Adding in handling of the child moved eventTed Gould2009-09-171-0/+9
|
* Commenting out the blocking on root waiting for an update.Ted Gould2009-09-111-0/+6
|
* Basic support for the sensitive property.Ted Gould2009-09-021-0/+1
|
* 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.
* Adding some defines for some common property values.Ted Gould2009-08-261-0/+5
|
* Spelling fix.Ted Gould2009-08-261-1/+1
|
* 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.
* Forgot some signal documentation.Ted Gould2009-08-251-0/+1
|
* Switching the prototype for type handlers so that it passes the client as well.Ted Gould2009-08-252-2/+2
|
* Okay, building in some type handlers now.Ted Gould2009-08-251-0/+4
|
* Signaling the realized event after it has all it's parameters.Ted Gould2009-08-252-0/+3
|
* Creating a realized signal on the menu items.Ted Gould2009-08-252-1/+21
|
* 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-202-3/+21
| | | | 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-202-5/+41
| | | | 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.
* Bad prototype for dealing with the new items added signal which also has the ↵Ted Gould2009-07-011-2/+2
| | | | position in it. This made it so the server was the position, which causes bad stuff to happen.
* Hiding a debug messageTed Gould2009-06-261-1/+1
|
* Add the property of the menuitems to check to see if they're the root node ↵Ted Gould2009-06-263-0/+47
| | | | 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-232-0/+39
| | | | make it so that this can go up the stack easier.
* Now we're also signalling when a child gets moved around.Ted Gould2009-06-232-1/+13
|
* Adding in the 'moved' signal and make it so that the 'added' signal has the ↵Ted Gould2009-06-233-6/+30
| | | | position in it.
* 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.