We discussed yesterday with Jamie and Christian, and the best would be to get this implemented in the usensord service. So the idea is that service would expose a property the settings application can change. Toolkit will not read any setting, but will call the Haptics as it did before. On the other hand, sensors service must check who was the caller of the vibration, to differentiate whether the call came from OSK or the app itself. It will then decide to vibrate or not, based on the setting.
So changes would need to be done on 1. usensord - expose the property system settings app can change, identify the caller and do or do not vibrate depending on the setting 2. system settings app should read/write this property 3. toolkit calls the haptics (vibrate) as it did before, without checking the enabled flag Now, how does this sound? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433590 Title: apparmor dbus denial for org.freedesktop.Accounts To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1433590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
