aboutsummaryrefslogtreecommitdiff
path: root/libindicator
Commit message (Collapse)AuthorAgeFilesLines
* Only build and use IndicatorNg in the gtk3 buildLars Uebernickel2013-01-181-1/+5
|
* Add IndicatorNgLars Uebernickel2013-01-183-1/+468
| | | | | | | IndicatorNg is an indicator object that reads an indicator service file and watches the bus for a corresponding service to appear. It turns the menus and actions exported by the service into an indicator entry.
* No newline at end of fileCharles Kerr2012-09-111-1/+2
|
* remove the cloak/decloak widget logicCharles Kerr2012-09-111-64/+3
|
* don't include build-time filenames in comments of the enum header filesEvgeni Golov2012-06-102-3/+3
| | | | | | | If we do, the header files may be different on each build. This is especially harmful when building multiple times for multiple architectures and expecting the files to be identical.
* indiator_service_manager_new*()'s name arguments were gchar*, make them ↵Charles Kerr2012-04-222-4/+4
| | | | const gchar*
* in indicator_image_helper_update(), test the image argument with ↵Charles Kerr2012-04-111-1/+1
| | | | GTK_IS_IMAGE before using it.
* Fix spelling/grammar errors in an error message.Charles Kerr2012-04-021-1/+1
|
* Setting again the variables as constMarco Trevisan (Treviño)2012-04-011-2/+2
|
* Indicator Service Manager: we don't have to free values if got with &s from ↵Marco Trevisan (Treviño)2012-04-011-3/+0
| | | | | | variant See http://is.gd/EyhAhP
* 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
|/
* 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-021-15/+95
|\
| * 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
| |
| * 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
| |
| * Changing our defines around to make sure to mark things the way that we ↵Ted Gould2012-02-271-11/+14
| | | | | | | | think about them.
* | 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
|/
* Removing unenforcable constsTed Gould2012-02-222-4/+4
|
* 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.
* Plug memory leak in parse_keyfile function.Daniel d'Andrada2012-02-091-0/+1
|
* IndicatorObject: update object parent in any case.Marco Trevisan (Treviño)2012-01-251-6/+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
|
* Bumping the ABI versionTed Gould2012-01-231-1/+1
|
* Add visibility concept to the default indicator objectTed Gould2012-01-233-31/+338
|\
| * "bzr merge lp:indicator" + conflict resolution in tests suiteCharles Kerr2012-01-234-2/+41
| |\
| * | another iteration of the indicator-object visibility support patch, ↵Charles Kerr2012-01-232-168/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | incorporating ideas from discussion with ted - some functions were public when they should have been private - the hide/show handler is now a virtual function & is documented in indicator-object.h - added unit tests - the GSettings monitor has been removed
| * | fix bugs in IndicatorObject's visibility support.Charles Kerr2012-01-201-138/+161
| | |
| * | Better implementation.Charles Kerr2012-01-132-119/+227
| | | | | | | | | | | | | | | This version handles the bootstrapping conditions better, and also refs+detaches the GtkMenu for safekeeping between removed->added events s.t. it can keep being reused.
| * | initial revision for GSettings/GtkMenu visibility supportCharles Kerr2012-01-123-12/+272
| | |
* | | Set the parent_object on the default entryTed Gould2012-01-191-0/+1
| | |
* | | Adding a parent object pointer to the entryTed Gould2012-01-191-0/+2
| |/ |/|
* | Adding a window ID function to pass the window IDTed Gould2012-01-192-0/+37
|\ \
| * | Clearing the entry function pointersTed Gould2012-01-131-0/+4
| | |
| * | Handling the activate_window function and going up the stackTed Gould2012-01-131-0/+7
| | |
| * | Documenting what this stuff doesTed Gould2012-01-131-0/+16
| | |
| * | Adding an activate window function, that can also be virtual! Ted Gould2012-01-132-0/+10
| | |
* | | Adding test coverage checkingTed Gould2012-01-131-0/+2
|\ \ \ | |/ / |/| |
| * | Added coverage reporting via gcov config and targets.Allan LeSage2011-12-061-0/+2
| |/
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 01:20:22 +0000