aboutsummaryrefslogtreecommitdiff
path: root/src/profile.vala
Commit message (Collapse)AuthorAgeFilesLines
* src/profile.vala: Add tooltip.Mike Gabriel2022-09-051-0/+1
|
* Hide bluetooth icon on hardware without bluetooth supportRobert Tari2022-08-011-2/+9
| | | | fixes https://github.com/AyatanaIndicators/ayatana-indicator-bluetooth/issues/42
* src/*.vala: make the switch item & action QMenuModel compatibleRatchanan Srirattanamet2022-06-221-3/+6
| | | | | | | | | | | | | | | | | | | | | | | QMenuModel, inheritting code from GTK, will consider the menu item not "activatable" if the item's "target" [1] doesn't match the corresponding action's parameter. Since we take a boolean as action's parameter (and we can't change action's parameter easily since it's semi-public), we instead have to pass "target". Taking a page from the slider menu items, pass "true" as the target will make QMenuModel considers the item activatable and reflect the right state. And while we're at it, restore the ability to use g_action_change_state to change the state. This allows the clients that still support Canonical's indicator (e.g. Lomiri) to not have to distinguish between that and Ayatana's. This, again, is taken from how the slider menu items work. [1] i.e. the parameter to pass when activating the action. See https://wiki.gnome.org/Projects/GLib/GApplication/DBusAPI#Attributes Related: https://github.com/AyatanaIndicators/qmenumodel/issues/21
* src/*.vala: Follow-up fix for dd2f32e2 (fixing GPL-3 license texts in file ↵Mike Gabriel2020-10-301-2/+2
| | | | headers).
* src/*.vala: Fix license headers having been a mix of GPL and LGPL license ↵Mike Gabriel2020-10-301-2/+2
| | | | text fragments. Adapt to GPL-3, fully.
* src/*: Switch to new activate state connect approach, rathern than using ↵Robert Tari2020-10-261-6/+3
| | | | notify["state"].connect.
* src/*: Scope and white-space fixes.Robert Tari2020-10-261-0/+1
|
* Switch over from Ubuntu System Indicator to Ayatana System Indicator.Robert Tari2020-10-251-4/+4
|
* mark the 'Bluetooth' menuitem for translationCharles Kerr2013-12-061-1/+1
|
* support header icon states as per the spec -- different icons for disabled, ↵Charles Kerr2013-12-061-3/+9
| | | | enabled, and enabled-with-connected-devices
* don't leak implicitly-created GVariantsCharles Kerr2013-10-241-5/+5
|
* if /dev/rfkill doesn't exist or isn't writable, then try to handle bluetooth ↵Charles Kerr2013-10-111-8/+5
| | | | toggles simply by toggling bluez Adapters' Powered property
* add an action whose state shows whether or not bluetooth is supported by the ↵Charles Kerr2013-10-101-0/+12
| | | | hardware, used by ubuntu-system-settings
* use the change-state signal to handle bluetooth-enabled change requests. h/t ↵Charles Kerr2013-09-231-3/+3
| | | | larsu
* add a title to the header's action stateCharles Kerr2013-09-111-0/+1
|
* create Profile.root_action in Profile's constructor.Charles Kerr2013-08-091-16/+6
|
* on shutdown, unexport the menus and unown the bus nameCharles Kerr2013-08-091-2/+13
|
* copyediting: whitespace, type inferenceCharles Kerr2013-08-061-3/+3
|
* copyediting: fix lines that wrapCharles Kerr2013-08-061-7/+24
|
* copyediting: don't use 'this.' when it's not neededCharles Kerr2013-08-061-2/+2
|
* promote shared functions up from Desktop to Profile so that Phone can use it tooCharles Kerr2013-08-051-8/+97
|
* pass the SimpleActionGroup handle into the profile object so that ↵Charles Kerr2013-08-051-2/+0
| | | | dynamically-added actions can get added/exported
* fully implement the bluez/device backend. in the desktop profile, add ↵Charles Kerr2013-08-051-2/+2
| | | | menuitems for the devices.
* change the 'BluetoothMenu' superclass to 'Profile'Charles Kerr2013-08-031-0/+54