aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* We're going to need a new version for this change.Ted Gould2009-08-261-1/+1
|
* Having new children processed on realizationTed Gould2009-08-261-3/+2
|
* Adding in a default type handler, incase it's configured, but not set by ↵Ted Gould2009-08-261-0/+2
| | | | clients.
* Making some separator tests and a visibility one as well.Ted Gould2009-08-261-5/+5
|
* Centralize visiblity processing and changes to the prop value.Ted Gould2009-08-261-4/+17
|
* Adding some defines for some common property values.Ted Gould2009-08-261-0/+5
|
* Spelling fix.Ted Gould2009-08-261-1/+1
|
* Making a separatorTed Gould2009-08-261-9/+11
|
* Use the label Luke! It helps.Ted Gould2009-08-261-1/+1
|
* Instead of directly appending items, make it so that they're not connected ↵Ted Gould2009-08-261-1/+12
| | | | until they're realized.
* Adding a warning, showing the widget and moving the new signal to ensure ↵Ted Gould2009-08-261-3/+5
| | | | everything is setup first
* Adding a type of 'menuitem' on all of these.Ted Gould2009-08-251-67/+67
|
* Ah, bother. Check NULL. Brain fart.Ted Gould2009-08-251-1/+1
|
* Now we're building the child/parent relationship using the activation type ↵Ted Gould2009-08-251-2/+4
| | | | function.
* 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-253-10/+9
|
* Code reshuffle. Now a warning on new items and fleshing out the type-based ↵Ted Gould2009-08-251-9/+19
| | | | functions.
* Okay, building in some type handlers now.Ted Gould2009-08-252-0/+34
|
* 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.
* Seems intltool changed slightlyTed Gould2009-08-201-1/+1
|
* Switching the new signal to be after the properties are gotten and adding a ↵Ted Gould2009-08-202-5/+41
| | | | hashtable for type handlers.
* AM 1.11 silenceTed Gould2009-08-201-0/+2
|
* Merging in the development branchesTed Gould2009-08-0446-703/+3844
|\
| * Heh, turns out we need to actually signal people across DBus or nothing ↵Ted Gould2009-07-201-0/+21
| | | | | | | | works. Who'd a thought.
| * Print on clickTed Gould2009-07-201-0/+8
| |
| * 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.
| * Adding a really simple test to add items to a stack.Ted Gould2009-07-013-2/+60
| |
| * Hiding a debug messageTed Gould2009-06-261-1/+1
| |
| * Wait for the signal about the root changing instead of forcing it here. ↵Ted Gould2009-06-261-2/+0
| | | | | | | | It'll have to change from the beginning state that we just had it in. And since we're singled threaded ther was no way for it to change in those few lines of code.
| * Removing the old is_root and now using the new property on the menuitems for ↵Ted Gould2009-06-262-10/+3
| | | | | | | | that task.
| * 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.
| * Ignoring more tests files.Ted Gould2009-06-251-0/+2
| |
| * For some reason the kill switch was missing on this one. Weird.Ted Gould2009-06-251-0/+4
| |
| * Some debug messages and a forcing the initial root reset at the start.Ted Gould2009-06-251-0/+6
| |
| * Okay, now we have these guys doing something, let's roll.Ted Gould2009-06-251-3/+16
| |
| * Fleshing out the root changed function, but that's led to another couple ↵Ted Gould2009-06-251-2/+37
| | | | | | | | that need to get figured out as well.
| * Make it so that getting the menuitem will create it in cases where it's not ↵Ted Gould2009-06-252-6/+16
| | | | | | | | created. This removes the chance of a race between the various functions.
| * Making it so that we don't have any gtk events or handling of the root node. ↵Ted Gould2009-06-251-0/+13
| | | | | | | | It's a special node, we need to leave it alone.
| * Adding the client to the child related functionsTed Gould2009-06-251-10/+10
| |
| * Merging in the updated gtkmenu branch with tests.Ted Gould2009-06-2523-0/+1380
| |\
| | * Merging in Ara's work on getting us some gtkmenu tests in mago. Woo hoo. ↵Ted Gould2009-06-2523-0/+1380
| | |\ | | | | | | | | | | | | Now some real tests.
| | | * Changing the clean rule to be distclean-local which makes more sense.Ted Gould2009-06-251-1/+2
| | | |
| | | * Removing the built python directory and destroying the mago results.Ted Gould2009-06-251-0/+3
| | | |
| | | * Making it so that we don't distribute the .xml and .py file, but build them ↵Ted Gould2009-06-251-2/+0
| | | | | | | | | | | | | | | | everytime.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 05:07:11 +0000