Merge branch 'update_README' into 'main'
Update README.md See merge request Librem5/feedbackd!88
This commit is contained in:
@@ -73,6 +73,10 @@ events. This will allow us to act as a system sound library so
|
|||||||
applications only need to call into this library and things like
|
applications only need to call into this library and things like
|
||||||
the quiet and silent profile work out of the box.
|
the quiet and silent profile work out of the box.
|
||||||
|
|
||||||
|
Any feedback triggered by a client via an event will be stopped latest when the
|
||||||
|
client disconnects from DBus. This makes sure all feedbacks get canceled if the
|
||||||
|
app that triggered it crashes.
|
||||||
|
|
||||||
## Feedback theme
|
## Feedback theme
|
||||||
Events are then mapped to a specific type of feedback (sound, led, vibra) via a
|
Events are then mapped to a specific type of feedback (sound, led, vibra) via a
|
||||||
device specific theme (since devices have different capabilities).
|
device specific theme (since devices have different capabilities).
|
||||||
@@ -200,6 +204,11 @@ Run feedbacks for event `message-new-instant` for 10 seconds:
|
|||||||
_build/cli/fbcli -t 10 -E alarm-clock-elapsed
|
_build/cli/fbcli -t 10 -E alarm-clock-elapsed
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Python example
|
||||||
|
|
||||||
|
There's an `example.py` script in the example/ folder of the
|
||||||
|
repository demonstrating how to trigger feedback via an event.
|
||||||
|
|
||||||
## Per app profiles
|
## Per app profiles
|
||||||
One can set the feedback profile of an individual application
|
One can set the feedback profile of an individual application
|
||||||
via `GSettings`. E.g. for an app with app id `sm.puri.Phosh`
|
via `GSettings`. E.g. for an app with app id `sm.puri.Phosh`
|
||||||
|
|||||||
Reference in New Issue
Block a user