spec: Clarify feedback noisiness

The old wording could be interpreted as the feedback being discarded if
it's noisier than the currently selected profile which is not the case.

Also take the new per application settings into account.
This commit is contained in:
Evangelos Ribeiro Tzaras
2022-06-24 00:51:51 +02:00
parent 17c1c2aa24
commit bdf4403b9d
+10 -6
View File
@@ -25,14 +25,18 @@ theme for a given device.
# Implementation
When an application triggers feedback for an event in the feedback
daemon the daemon selects the provided feedback like this:
When an application requests feedback for an event via the feedback daemon
the daemon selects the provided feedback like this,
capping the noisiness for each limit:
1. feedbacks from a nosier profiles like the currently selected are
ignored
1. The currently selected profile provides the (global) upper limit for noisiness
2. All other feedbacks for this event are selected and run to provide
feedback to the user
2. Per application settings impose another upper limit
3. Per event noisiness is the last noisiness constraint
4. All feedback consistent with the resulting limit are selected
and run to provide the feedback to the user
With the above a feedback theme in YAML format could look like: