aboutsummaryrefslogtreecommitdiff
path: root/libindicator
Commit message (Collapse)AuthorAgeFilesLines
* IndicatorNG: Reverse the scroll delta on left scroll eventsMarco Trevisan (Treviño)2014-07-161-2/+6
| | | | As it happens for left scroll events.
* Don't load using the icon info structure if it's a bytes icon.William Hua2014-03-291-1/+1
|
* IndicatorImageHelper: let's use the actual icon file if its height is less ↵Marco Trevisan (Treviño)2014-03-031-14/+15
| | | | than ICON_SIZE
* IndicatorLoader: Make sure that we load the icon at its original size, if ↵Marco Trevisan (Treviño)2014-03-031-7/+20
| | | | | | not higher than IMAGE_SIZE In this way icons such as the battery one won't be shrunk.
* ImageHelper: set image from icon name if we have the filenameMarco Trevisan (Treviño)2014-02-281-1/+1
|
* IndicatorImageHelper: always try to use a GIcon or the file-name as source ↵Marco Trevisan (Treviño)2014-02-281-37/+27
| | | | | | | | | | | | of the Gdk image We don't need to fallback to pure pixbuf, unless an indicator provided a custom icon that is not in the current theme path. This helps a lot in reducing the Unity7 workload as this decreases the cases where we need to encode the pixbuf contents, send them via dbus to unity, encode them back, reload to a new pixbuf... Also thanks to this, the library clients can load the actual icon, scaled at the value they want.
* IndicatorObject: add parent_window parameter to IndicatorEntry Marco Trevisan (Treviño)2014-02-182-3/+8
|\
| * IndicatorObject: add parent_window parameter to IndicatorEntryMarco Trevisan (Treviño)2014-02-132-3/+8
| |
* | indicator-ng: support "submenu-action" on root menu itemsLars Uebernickel2014-01-291-0/+34
|/ | | | | | | | | | Treat "submenu-action" attributes on the root menu item in the same way that gtk+ does. If that attribute exists, it must reference an action with boolean state that is set to 'true' whenever a corresponding indicator menu is open. We need this for root items because they are not handled by gtk's menu tracker. Nested submenus already get this.
* Use named icons rather than (deprecated) stock items.Colin Watson2013-12-202-3/+3
|
* Don't treat deprecation warnings as errorsLars Uebernickel2013-12-191-1/+1
|
* Allow setting different positions for each profile in indicator filesLars Uebernickel2013-10-291-0/+3
|\ | | | | | | | | | | | | | | The 'Position' key in a profile section has precedence over the global 'Position' key, but otherwise the same semantics. We need this along with lp:~larsu/unity8/per-profile-indicator-positions to enable different positioning on the desktop and phone. Approved by PS Jenkins bot, Charles Kerr.
| * Allow setting per-profile positions in indicator filesLars Uebernickel2013-10-101-0/+3
| | | | | | | | | | | | The 'Position' key in a profile section has precedence over the global 'Position' key, but otherwise the same semantics.
* | minor cleanup in the dispose() and finalize() functionsCharles Kerr2013-10-231-16/+4
| |
* | When we can't get a handle to the system bus, exit gracefully instead of ↵Charles Kerr2013-10-231-1/+4
| | | | | | | | crashing.
* | indicator-ng: always create entry.label and entry.imageLars Uebernickel2013-10-171-6/+3
| | | | | | | | | | | | | | | | | | | | | | They used to be created lazily when the root menu item changed to include and image or a label. However, there is no way to notify a panel that this happened. Panels connect to notify signals on these widgets when an entry gets added. If the widgets don't exist from the very beginning, the panel won't update when they change.
* | Warn when an indicator doesn't get respawned anymoreLars Uebernickel2013-10-161-1/+5
|/
* Remove debug messageLars Uebernickel2013-09-091-2/+0
|
* Support x-canonical-secondary actionLars Uebernickel2013-09-091-0/+27
| | | | | | | An attribute for the root menu action may contain an action name. If it exists, the action is activated whenever the middle mouse button is pressed on the indicator.
* Support "x-canonical-scroll-action"Lars Uebernickel2013-09-091-5/+32
| | | | | | | An attribute that can be set on the root menu item. If it exists, it must point to an action that is activatable with a int32 parameter. It is activated on scroll events. The parameter signifies magnitude and direction of the scroll.
* IndicatorDesktopShortcut: fix indentationMarco Trevisan (Treviño)2013-08-221-1/+1
|
* IndicatorDesktopShortcuts: restore previous working dir if we changed itMarco Trevisan (Treviño)2013-08-221-6/+22
|
* IndicatorDesktopShortcuts: use g_key_file_get_string for pathMarco Trevisan (Treviño)2013-08-091-5/+2
|
* IndicatorDesktopShortcuts: add support to Path key for shortcut itemsMarco Trevisan (Treviño)2013-08-081-3/+15
|
* IndicatorDesktopShortcuts: free groupheaderMarco Trevisan (Treviño)2013-07-171-0/+2
|
* indicator-object: g_return_if_fail -> g_return_val_if_failLars Uebernickel2013-06-281-1/+1
|
* Allow indicators to tell the panel where they want to appearLars Uebernickel2013-06-283-1/+57
| | | | | | Only implemented in IndicatorNg right now, which gets that information from the indicator file.
* in indicator_ng_service_started(), the result's variant type should be ↵Charles Kerr2013-06-271-6/+10
| | | | parsed as '(u)' rather than 'u'
* in indicator_ng_update_entry, unconditionally call set_label, set_icon, ↵Charles Kerr2013-06-161-6/+3
| | | | set_accessible. Previously these were only called if the respective fields weren't NULL, which made it impossible to, for example, turn off a label or icon once it had been set.
* indicator-ng: properly fail when keyfile doesn't existLars Uebernickel2013-06-071-1/+1
|
* Merge lp:~larsu/new-indicator-file-formatLars Uebernickel2013-06-071-31/+60
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IndicatorNg: update indicator file format The old file format had some shortcomings: (1) It was impossible to efficiently reuse a menu for different profiles, because the profile name was implicit in the object path. The only way to do this was to export the same menu twice. Now, object paths have to be set explicitly in the indicator file. (2) The well-known dbus name of a service and the name of its service file were similar but slightly different (com.canonical.indicator.test vs com.canonical.test.indicator), which caused some confusion on when to use which. Now, the file name *is* the bus name, and the `BusName` key has been dropped. The new file format is documented in README.
| * indicator-ng: fix crashLars Uebernickel2013-05-291-5/+2
| |
| * IndicatorNg: update indicator file formatLars Uebernickel2013-05-241-12/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The old file format had some shortcomings: (1) It was impossible to efficiently reuse a menu for different profiles, because the profile name was implicit in the object path. The only way to do this was to export the same menu twice. Now, object paths have to be set explicitly in the indicator file. (2) The well-known dbus name of a service and the name of its service file were similar but slightly different (com.canonical.indicator.test vs com.canonical.test.indicator), which caused some confusion on when to use which. Now, the file name *is* the bus name, and the `BusName` key has been dropped. The new file format is documented in README.
| * refactor indicator_ng_initable_initLars Uebernickel2013-05-241-22/+16
| | | | | | | | | | This makes the flow a bit more apparent. Also gets rid of a goto.
* | IndicatorDesktopShortcuts: Use the proper way to create an AppInfo from ↵Marco Trevisan (Treviño)2013-05-291-23/+11
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | command-line Removed the hack that we used to create a .desktop app-info from a locally generated keyfile, using g_app_info_create_from_commandline instead. Fixes: https://bugs.launchpad.net/bugs/1168373. Approved by PS Jenkins bot, Ted Gould.
| * | IndicatorDesktopShortcuts: some code cleanupMarco Trevisan (Treviño)2013-04-191-3/+1
| | |
| * | IndicatorDesktopShortcuts: initialize flags using the default defineMarco Trevisan (Treviño)2013-04-121-1/+2
| | |
| * | IndicatorDesktopShortcuts: Use the proper way to create an AppInfo from ↵Marco Trevisan (Treviño)2013-04-121-21/+10
| | | | | | | | | | | | | | | | | | | | | command-line We remove the workaround that we used to create a .desktop app-info from a locally generated keyfile.
* | | Handling the deprecation of gtk_icon_info_free()Ted Gould2013-05-291-0/+6
| |/ |/|
* | Code clean-up.William Hua2013-05-191-31/+27
| |
* | Clean up error checking.William Hua2013-04-261-31/+22
| |
* | Don't free label and accessible_desc.William Hua2013-04-261-5/+2
| |
* | [ William Hua ]William Hua2013-04-222-24/+72
|/ | | | | | | | | | | | * debian/control: - Bump GLib to 2.37. * configure.ac: - Bump GLib to 2.37. * libindicator/indicator-image-helper.c: - Support display of GBytesIcons. * libindicator/indicator-ng.c: - Change action state icon type to GVariant.
* IndicatorDestkopShortcuts: add StartupNotify parameter in our internal fake ↵Marco Trevisan (Treviño)2013-04-091-5/+19
| | | | | | | .desktop file Otherwise GAppInfo won't pass the relevant platform-data to the Application launched. Plus, fix the docs.
* IndicatorDestkopShortcuts: fix indentationMarco Trevisan (Treviño)2013-04-051-8/+8
|
* IndicatorDestkopShortcuts: add missing include and deprecate old functionMarco Trevisan (Treviño)2013-04-051-0/+3
|
* IndicatorDestkopShortcuts: add ↵Marco Trevisan (Treviño)2013-04-052-2/+11
| | | | | | | indicator_desktop_shortcuts_nick_exec_with_context It allows to pass a GAppLaunchContext to pass platform-data when launching actions.
* indicator-ng: allow a dictionary as the root action's stateLars Uebernickel2013-03-211-11/+20
| | | | | | | | | Hopefully, this is more straightforward to use than (sssb). It's also extensible. (sssb) is still supported for backwards compatibility, but I wouldn't recommend using it anymore.
* Revert: indicator-ng: allow a dictionary as the root action's stateMathieu Trudel-Lapierre2013-03-181-20/+11
|
* indicator-ng: allow a dictionary as the root action's stateLars Uebernickel2013-03-131-11/+20
| | | | | | | | | Hopefully, this is more straightforward to use than (sssb). It's also extensible. (sssb) is still supported for backwards compatibility, but I wouldn't recommend using it anymore.