aboutsummaryrefslogtreecommitdiff
path: root/src/desktop.vala
Commit message (Collapse)AuthorAgeFilesLines
* src/*: Switch to new activate state connect approach, rathern than using ↵Robert Tari2020-10-261-12/+6
| | | | notify["state"].connect.
* src/*: Scope and white-space fixes.Robert Tari2020-10-261-2/+2
|
* Make indicator aware of running inside the MATE desktop environment.Robert Tari2020-10-261-0/+4
|
* Make dependency on liburl-dispatcher optional.Robert Tari2020-10-261-3/+17
|
* Switch over from Ubuntu System Indicator to Ayatana System Indicator.Robert Tari2020-10-251-5/+5
|
* Correctly use XDG_CURRENT_DESKTOPRobert Ancell2016-06-071-1/+14
|
* Remove the "browse" action since there is no working backendSebastien Bacher2016-05-121-0/+5
|
* under unity8 start system-settings instead unity-control-centerSebastien Bacher2015-08-271-1/+3
|
* Support Bluez 5Robert Ancell2014-12-111-12/+0
| | | | | | | | | When enabling/disabling and setting discoverability we now do this for all adapters. This requires us to remove the "Set Up New Device" item since gnome-bluetooth no longer has a bluetooth wizard stand alone application. Instead we rely on the unity-control-center panel for device setup.
* Only run unity-control-center under unityRobert Ancell2014-01-221-1/+1
|
* Use unity-control-center if it is availableRobert Ancell2014-01-101-1/+4
|
* on the desktop, show a bluetooth indicator if the hardware supports ↵Charles Kerr2013-12-061-2/+2
| | | | bluetooth and if the user has chosen for the indicator to be visible.
* don't leak implicitly-created GVariantsCharles Kerr2013-10-241-6/+6
|
* Desktop menu: mark "Visible" menu item label for translationLars Uebernickel2013-10-211-1/+1
|
* when listening to notify events from bluetooth to update desktop indicator ↵Charles Kerr2013-10-141-1/+1
| | | | visibility, add a specifier for which event to monitor
* if /dev/rfkill doesn't exist or isn't writable, then try to handle bluetooth ↵Charles Kerr2013-10-111-5/+1
| | | | 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/+1
| | | | hardware, used by ubuntu-system-settings
* Don't use deprecated GSimpleActionGroup APIs.Charles Kerr2013-08-221-2/+2
|
* create Profile.root_action in Profile's constructor.Charles Kerr2013-08-091-1/+1
|
* copyediting: whitespace, type inferenceCharles Kerr2013-08-061-9/+18
|
* templated strings need to begin with a '@'Charles Kerr2013-08-061-1/+1
|
* copyediting: fix lines that wrapCharles Kerr2013-08-061-18/+46
|
* promote shared functions up from Desktop to Profile so that Phone can use it tooCharles Kerr2013-08-051-78/+17
|
* in phone and desktop, make 'action_state_for_root' private -- it's no longer ↵Charles Kerr2013-08-051-2/+2
| | | | in the Profile superclass.
* pass the SimpleActionGroup handle into the profile object so that ↵Charles Kerr2013-08-051-17/+17
| | | | dynamically-added actions can get added/exported
* fully implement the bluez/device backend. in the desktop profile, add ↵Charles Kerr2013-08-051-16/+176
| | | | menuitems for the devices.
* change the 'BluetoothMenu' superclass to 'Profile'Charles Kerr2013-08-031-18/+16
|
* add a bluetooth backend to track bluetooth being enabled, being hard/soft ↵Charles Kerr2013-08-011-34/+87
| | | | blocked, and its devices.
* add per-profile icons and initial menus w/settings sectionCharles Kerr2013-08-011-0/+99