lp://qastaging/~ken-vandine/ubuntu-system-settings/haptic_entry_component

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://qastaging/ubuntu-system-settings at revision 1627

Jonas G. Drange (community): Approve on 2016-03-23

Diff: 23 lines (+2/-0)

2 files modified

src/qml/CategoryGrid.qml (+1/-0)
src/qml/UncategorizedItemsView.qml (+1/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1560571: No haptic feedback on about and reset entries

Undecided

Fix Released

Link a bug report

Related blueprints

1622. By Ken VanDine on 2016-03-22

Handle the Haptics.play in the UncategorizedItemsView and CategoryGrid instead of in the plugin themselves

1621. By Ken VanDine on 2016-03-22

Play haptic feedback when selecting About and Reset from the main view.

1620. By CI Train Bot Account on 2016-03-16

Releasing 0.3+16.04.20160316.1-0ubuntu1

1619. By dobey on 2016-03-16

Fix the CMakeLists.txt to handle settings.js generation and translations better. Fixes: #1555623

1618. By Jonas G. Drange on 2016-03-16

Replace usage of backgroundText from the selected palette for labels with baseText from normal palette.
Approved by: Ken VanDine

1617. By Michael Terry on 2016-03-16

Use geonames library instead of timezonemap library to search city names, which gives us slightly better sorting (and future improvements)
Approved by: Jonas G. Drange

1616. By CI Train Bot Account on 2016-03-14

Releasing 0.3+16.04.20160314.4-0ubuntu1

1615. By Jonas G. Drange on 2016-03-14

New VPN panel with happy path test Fixes: #1495553
Approved by: Ken VanDine

1614. By CI Train Bot Account on 2016-03-14

Releasing 0.3+16.04.20160314-0ubuntu1

1613. By Simon Fels on 2016-03-14

Rework Bluetooth device discovery handling

We need to make sure that bluetooth device discovery is never executed while we're not running. BlueZ itself takes care about stopping when we're exiting but while we're running we need to make sure we only run it when the user is using the app. This implements a ref counting logic to keep track of who blocks discovery. Next to us being paused we need to also stop discovery when a device gets connected/disconnected.
Approved by: Ken VanDine