aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Drop lomiri-url-dispatcherRobert Tari2021-08-281-7/+0
|
* Replace code with libayatana-common functionsRobert Tari2021-08-283-42/+17
| | | | | | | | - CMakeLists.txt: Add libayatana-common build dependency - src/CMakeLists.txt: Add AyatanaCommon package to ayatana-indicator-bluetooth-service - src/phone.vala: Replace local code with libayatana-common functions - src/desktop.vala: Replace local code with libayatana-common functions - vapi/lomiri-url-dispatcher.vapi: Drop file
* Use CMAKE_INSTALL_FULL_*DIR locations for installationRobert Tari2021-08-041-1/+1
|
* src/CMakeLists.txt: Fix loading VAPI file for lomiri-url-dispatcher.Mike Gabriel2021-02-031-1/+1
|
* Finalize incomplete switch to Lomiri URL Dispatcher.Mike Gabriel2021-02-032-2/+2
|
* Show devices in sectionsRobert Tari2020-12-221-1/+10
|
* Fix build warningsRobert Tari2020-12-222-0/+8
|
* desktop.vala: Do not hide the indicatorRobert Tari2020-12-212-4/+7
| | | | fixes #15
* src/*.vala: Follow-up fix for dd2f32e2 (fixing GPL-3 license texts in file ↵Mike Gabriel2020-10-309-18/+18
| | | | headers).
* src/*.vala: Fix license headers having been a mix of GPL and LGPL license ↵Mike Gabriel2020-10-309-18/+18
| | | | text fragments. Adapt to GPL-3, fully.
* Port from autotools to CMake.Mike Gabriel2020-10-262-39/+180
|
* src/*: Switch to new activate state connect approach, rathern than using ↵Robert Tari2020-10-262-18/+9
| | | | notify["state"].connect.
* src/bluez.vala: Make BLUEZ_BUSNAME 'const string' (not 'static const string').Robert Tari2020-10-261-1/+1
|
* src/*: Scope and white-space fixes.Robert Tari2020-10-264-4/+5
|
* Make indicator aware of running inside the MATE desktop environment.Robert Tari2020-10-261-0/+4
|
* Switch from GNOMELOCALEDIR to LOCALEDIR variable name.Robert Tari2020-10-261-1/+1
|
* Make dependency on liburl-dispatcher optional.Robert Tari2020-10-263-3/+27
|
* Switch over from Ubuntu System Indicator to Ayatana System Indicator.Robert Tari2020-10-254-16/+16
|
* 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
|
* in bluez.vala, silence a startup g_warning by calling ↵Charles Kerr2016-02-141-8/+15
| | | | init_bluez_state_vars() before we start listening for org.bluez on the bus
* in bluez.vala, update our state properties when org.bluez vanishes from the busCharles Kerr2016-02-141-3/+10
|
* in bluez.vala, create a symbolic name for bluez' busnameCharles Kerr2016-02-141-4/+5
|
* (trivial) remove trailing whitespaceCharles Kerr2016-02-141-2/+2
|
* in bluez.vala, watch for org.bluez to be owned/unowned on the system busCharles Kerr2016-02-141-11/+34
|
* Check for NULL when getting cached properties Address and UUIDsRobert Ancell2015-09-281-4/+7
|
* under unity8 start system-settings instead unity-control-centerSebastien Bacher2015-08-271-1/+3
|
* Remove unused argument in DBus interfaceRobert Ancell2015-08-071-3/+3
|
* Support Bluez 5Robert Ancell2014-12-114-541/+173
| | | | | | | | | 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.
* Toggle rfkill again so that we have a chance of persisting the bluetooth ↵Mathieu Trudel-Lapierre2014-09-221-1/+1
| | | | state across reboots.
* 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
|
* mark the 'Bluetooth' menuitem for translationCharles Kerr2013-12-061-1/+1
|
* change the bluetooth.supported property whenever bluez' default adapter ↵Charles Kerr2013-12-061-0/+2
| | | | changes its object path.
* support header icon states as per the spec -- different icons for disabled, ↵Charles Kerr2013-12-061-3/+9
| | | | enabled, and enabled-with-connected-devices
* add a 'connected' property as a simple hook to whether or not we have any ↵Charles Kerr2013-12-062-1/+23
| | | | connected bluetooth devices
* 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-242-11/+11
|
* Desktop menu: mark "Visible" menu item label for translationLars Uebernickel2013-10-211-1/+1
|
* make org.bluez.Adapter's set_property() call nonblockingCharles Kerr2013-10-142-18/+7
|
* omit the rfkill killswitch altogether, leaving on/off to bluez via ↵Charles Kerr2013-10-141-1/+1
| | | | org.bluez.Adapter's Powered property
* 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 killswitch exists and is valid, prefer its use over toggling ↵Charles Kerr2013-10-141-11/+13
| | | | org.bluez.Adapter's Powered property
* if /dev/rfkill doesn't exist or isn't writable, then try to handle bluetooth ↵Charles Kerr2013-10-116-70/+128
| | | | 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-105-0/+21
| | | | hardware, used by ubuntu-system-settings
* Update settings URL to settings:///systemCharles Kerr2013-10-031-1/+1
|
* use url-dispatcher instead of invoking system-settings directly.Charles Kerr2013-09-252-1/+2
|
* 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
|
* Don't use deprecated GSimpleActionGroup APIs.Charles Kerr2013-08-222-3/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 02:41:36 +0000