aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* merge lp:~charlesk/libindicator/fix-disthook to fix auto-generation of ↵0.4.94Charles Kerr2012-03-292-2/+3
|\ | | | | | | AUTHORS and Changelog by looking for 'missing' in the directory where we told AC_CONFIG_AUX_DIR to put it.
| * look for 'missing' in ac_aux_dir rather than top_srcdir.Charles Kerr2012-03-292-2/+3
|/
* 0.4.94Charles Kerr2012-03-281-1/+1
|
* merge lp:~htorque/libindicator/fix-small-leak to fix a GError memory leak ↵Charles Kerr2012-03-261-0/+1
|\ | | | | | | reported in lp bug #965459
| * Free GError.Hernando Torque2012-03-261-0/+3
| |
* | fix minor memory leak when the proxy name changesCharles Kerr2012-03-161-2/+5
|/
* 0.4.930.4.93Ted Gould2012-03-071-1/+1
|
* merge lp:~ted/libindicator/lp719457 for Bug #719457Charles Kerr2012-03-051-1/+3
|\
| * Attaching bugTed Gould2012-03-020-0/+0
| |
| * Copying the name before using it to remove as it seems that the unwatch can ↵Ted Gould2012-03-021-1/+3
|/ | | | cause the name to be free'd in some cases. Odd, but valgrind can find it
* Support new FD.o Desktop ActionsTed Gould2012-03-022-20/+100
|\
| * Get the right group in exec too! Ted Gould2012-02-271-1/+15
| |
| * Handling the different group names when getting the name as wellTed Gould2012-02-271-1/+15
| |
| * Update test desktop fileTed Gould2012-02-271-5/+5
| |
| * Creating a warning for the legacy supportTed Gould2012-02-271-0/+1
| |
| * Adding a value for whether it should use the TargetEnvironment, I'm removing ↵Ted Gould2012-02-271-5/+4
| | | | | | | | the warning because we don't care to fix old stuff anymore
| * Use the appropriate list of nicks and groups to find our data nowTed Gould2012-02-271-2/+24
| |
| * Figure out what kind of actions we haveTed Gould2012-02-271-1/+17
| |
| * Adding a state variable to track what kind of actions we haveTed Gould2012-02-271-0/+11
| |
| * Attaching bugTed Gould2012-02-270-0/+0
| |
| * Changing our defines around to make sure to mark things the way that we ↵Ted Gould2012-02-271-11/+14
| | | | | | | | think about them.
* | lp:~charlesk/libindicator/fix-939061Charles Kerr2012-02-291-8/+3
|\ \ | |/ |/|
| * silence Coverity warning "PW.BRANCH_PAST_INITIALIZATION - CID 10615" ↵Charles Kerr2012-02-291-2/+1
| | | | | | | | | | | | | | reported in Bug #939061 Coverity is unhappy that the local variable "priv" is uninitialized if one of the goto branches is followed in this function. Since we only use priv once, a fairly clean way of sidestepping this warning is removing the local variable "priv" and instead using INDICATOR_OBJECT_GET_PRIVATE()'s return pointer directly.
| * tweak: use g_clear_object() instead of if-not-null-g_object_unref()Charles Kerr2012-02-291-6/+2
|/
* 0.4.920.4.92Ted Gould2012-02-231-1/+1
|
* Remove unenforcable constsTed Gould2012-02-222-4/+4
|\
| * Attaching bugTed Gould2012-02-220-0/+0
| |
| * Removing unenforcable constsTed Gould2012-02-222-4/+4
|/
* Adjusting timeout so it'll build on the buildds tooTed Gould2012-02-141-1/+1
|
* Explicitly listing gmodule as a library we're usingTed Gould2012-02-141-0/+2
|\
| * Explicity add gmodule in the list of required librariesTed Gould2012-02-141-0/+2
|/
* 0.4.910.4.91Ted Gould2012-02-141-1/+1
|
* indicator_object_set_visible: only emit entry-{added,removed} when ↵Lars Uebernickel2012-02-131-17/+8
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | visibility actually changed Emitting those signals is semantically incorrect. It also confused indicator-loader and the panel, because they are not checking whether an entry is already present in their entry-added handlers. This led to gtk warnings ("widget already has a parent") and strange effects, such as the same menu being added multiple times into the panel. This patch also makes indicator_object_dispose use indicator_object_set_visible (it was already doing something similar).
| * indicator_object_dispose: remove unneeded list of entriesLars Uebernickel2012-02-131-5/+1
| |
| * indicator_object_dispose: use _set_visible instead of reimplementing itLars Uebernickel2012-02-131-12/+2
| |
| * indicator_object_set_visible: no need to check for ENTRY_INITLars Uebernickel2012-02-131-4/+2
| |
| * indicator_object_set_visible: only emit entry-{added,removed} when ↵Lars Uebernickel2012-02-121-1/+8
|/ | | | | | | | | | | visibility actually changed Emitting those signals is semantically incorrect. It also confused indicator-loader and the panel, because they are not checking whether an entry is already present in their entry-added handlers. This led to gtk warnings ("widget already has a parent") and strange effects, such as the same menu being added multiple times into the panel.
* Free groupname after usageTed Gould2012-02-101-0/+1
|\
| * Plug memory leak in parse_keyfile function.Daniel d'Andrada2012-02-091-0/+1
|/
* Be more agressive in ensureing the parent_object value is available everywhere.Ted Gould2012-02-033-16/+67
|\
| * tests, DummyIndicatorSignaler: free the allocated memory.Marco Trevisan (Treviño)2012-02-031-5/+7
| |
| * Test loader: check also for parent changesMarco Trevisan (Treviño)2012-01-251-0/+4
| |
| * Tests: update dummy signaler to work with real IndicatorObjectEntryMarco Trevisan (Treviño)2012-01-252-12/+28
| | | | | | | | This fixes a crash due to the parent/unparent.
| * IndicatorObject: update object parent in any case.Marco Trevisan (Treviño)2012-01-251-6/+6
| |
| * Added better parent_object tests.Marco Trevisan (Treviño)2012-01-251-2/+6
| |
| * Indicator-Object: update the parent_object value only if the entry is valid.Marco Trevisan (Treviño)2012-01-251-4/+16
| |
| * IndicatorObject: correctly initialize the parent object.Marco Trevisan (Treviño)2012-01-251-1/+14
|/
* 0.4.900.4.90Ted Gould2012-01-241-1/+1
|
* Bumping the ABI versionTed Gould2012-01-231-1/+1
|
* Add visibility concept to the default indicator objectTed Gould2012-01-237-31/+590
|\
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 12:29:26 +0000