aboutsummaryrefslogtreecommitdiff
path: root/libindicator/indicator-object.c
Commit message (Collapse)AuthorAgeFilesLines
* 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-221-2/+2
|
* 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.
* 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
|
* Add visibility concept to the default indicator objectTed Gould2012-01-231-30/+324
|\
| * "bzr merge lp:indicator" + conflict resolution in tests suiteCharles Kerr2012-01-231-0/+35
| |\
| * | another iteration of the indicator-object visibility support patch, ↵Charles Kerr2012-01-231-165/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-131-118/+222
| | | | | | | | | | | | | | | 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-121-11/+268
| | |
* | | Set the parent_object on the default entryTed Gould2012-01-191-0/+1
| |/ |/|
* | 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-131-0/+8
|/
* Adding in secondary activate supportTed Gould2011-07-211-2/+19
|\
| * Dropping the x and y paramaters from the secondary activate signalTed Gould2011-07-211-5/+2
| |
| * Added support for secondary activate signal: i.e. middle-clickMarco Trevisan (Treviño)2011-07-091-2/+22
| | | | | | | | | | | | | | | | Secondary activate signal is designed to be used for a secondary kind of activation, for example using middle-click. It exports both the event time and the mouse position (this is mostly needed to follow the Status Notifier specifications).
* | Annotate the return value of indicator_object_get_entries so that the type ↵Robert Ancell2011-07-081-3/+3
|/ | | | in the list is known, also fix typo in docstring
* Clearing our local name_hint and ensuring we fill it if a function is provided.Ted Gould2011-07-051-0/+5
|
* Merging "scroll" and "scroll-entry" into the "entry-scrolled" signalMarco Trevisan (Treviño)2011-07-021-23/+4
| | | | | API change to merge the duplication of signals, as defined in the blueprint desktop-dx-o-indicators-review
* Adding a nice little checking functionTed Gould2011-03-221-0/+30
|
* Adding an environments variable and make a lifecycle for it.Ted Gould2011-03-221-3/+19
|
* Getting some stub functions inTed Gould2011-03-221-0/+34
|
* * accessible_name -> accessible_desc to better reflect the use of the content.Luke Yelavich2011-02-081-6/+25
| | | | | | * Add accessible-desc-update signal so that indicators can tell indicator-applet/unity that the accessible description has changed
* Merge from trunkLuke Yelavich2011-02-011-2/+23
|\
| * Added support for "signal-entry" signalMarco Trevisan (Treviño)2011-01-271-2/+23
| | | | | | | | | | | | | | | | libindicator support the new "scroll-entry" signal (which get called using the target entry as parameter too) I think that maybe we could simply rewrite the "scroll" signal, but I kept it there for compatibility reasons; however, actually just the indicator-sound should be fixed in case of switch...
* | Add accessible_name variable in indicator entry structureLuke Yelavich2011-01-181-0/+10
|/
* Fixing doc stringsTed Gould2011-01-101-2/+2
|
* Adding a virtual function for closing the menu and a wrapper for it.Ted Gould2011-01-091-0/+21
|
* Adding a function to check whether we should show the indicator with priority.Ted Gould2011-01-041-0/+24
|
* Making it a real signal nowTed Gould2011-01-041-0/+19
|
* Fleshing out the entry activate functionTed Gould2010-09-161-1/+6
|
* Breaking the ABI and adding a subclassable function.Ted Gould2010-09-161-1/+2
|
* Adding a function to push activate back down.Ted Gould2010-09-161-0/+19
|
* Adding in the signal for the menu showingTed Gould2010-09-141-17/+36
|
* Documentation fix.Cody Russell2010-03-171-1/+1
|
* Define IndicatorScrollDirection enum for scroll signal parameter.Cody Russell2010-03-161-2/+3
|
* Add 'scroll' signal.Cody Russell2010-03-151-3/+23
|
* No error on not having a get_location function. We'll just return zero.Ted Gould2010-01-151-1/+0
|
* Fleshing out the get_location function as much as they're implemented here.Ted Gould2010-01-151-0/+27
|
* Fixing the signal comments.Ted Gould2010-01-151-5/+13
|
* Setting up the move signal, which required custom marshallers.Ted Gould2010-01-151-0/+16
|
* 64-bit fix in that GTypes are not ints on 64-bitTed Gould2009-11-051-2/+2
|