Fix typos

This commit is contained in:
Luca Weiss
2020-10-26 08:21:05 +00:00
committed by Guido Gunther
parent e79a24b5ad
commit ed0253fc44
6 changed files with 9 additions and 9 deletions
+1 -1
View File
@@ -72,7 +72,7 @@ applications which will use the Feedback Theme Specification.
- power-plug: The power cable has been plugged in. - power-plug: The power cable has been plugged in.
- power-unplug: The power cable has been unplugged. - power-unplug: The power cable has been unplugged.
- alarm-clock-elapsed: A user configured alarm elapsed. - alarm-clock-elapsed: A user configured alarm elapsed.
- timeout-completed: A user configured timout completed (e.g. a stop watch). - timeout-completed: A user configured timeout completed (e.g. a stop watch).
### Actions ### Actions
+1 -1
View File
@@ -65,7 +65,7 @@ uses a format [similar to the above in JSON](./data/default.json).
# Recommendations # Recommendations
- The silent theme shoud not produce any audible feedback. This includes - The silent theme should not produce any audible feedback. This includes
the buzzing of haptic motors. the buzzing of haptic motors.
- The quiet theme should not play any sounds. Haptic motors and LEDs can - The quiet theme should not play any sounds. Haptic motors and LEDs can
be used. be used.
+3 -3
View File
@@ -34,7 +34,7 @@ feedbackd (0.0.0+git20200726) amber-phone; urgency=medium
reason in the actual test function anyway. reason in the actual test function anyway.
* tests: Test event not found case too * tests: Test event not found case too
* feedback-manager: Deeply free the feedback list. * feedback-manager: Deeply free the feedback list.
Instead of freeing each elemnt after each iteration and then the list Instead of freeing each element after each iteration and then the list
itself at the very end just fully free the list. g_autoslist does itself at the very end just fully free the list. g_autoslist does
not work well on oder glib so do that manually. not work well on oder glib so do that manually.
This is just cosmetics. This is just cosmetics.
@@ -59,7 +59,7 @@ feedbackd (0.0.0+git20200714) amber-phone; urgency=medium
[ Guido Günther ] [ Guido Günther ]
* lfb-event: Clarify return values of `finished` functions. * lfb-event: Clarify return values of `finished` functions.
They just inidicate that we talked to feedbackd succesfully. They just inidicate that we talked to feedbackd successfully.
* lfb-event: Connect done handler in async case too. * lfb-event: Connect done handler in async case too.
Otherwise the event state is not updated properly Otherwise the event state is not updated properly
* tests: Don't quit mainloop on event end. * tests: Don't quit mainloop on event end.
@@ -97,7 +97,7 @@ feedbackd (0.0.0+git20200707) amber-phone; urgency=medium
* docs: Add manpages (Closes: #12) * docs: Add manpages (Closes: #12)
* data: Drop phone-missed-call in 'quiet' profile. Only want LEDs there. * data: Drop phone-missed-call in 'quiet' profile. Only want LEDs there.
* feedbackd: Add helper to set up permissions for LEDs. * feedbackd: Add helper to set up permissions for LEDs.
This helper knows about the tiggers and necessary permission. This helper knows about the triggers and necessary permission.
It's intended to be run via udev. It's intended to be run via udev.
* debian: Setup leds via udev. * debian: Setup leds via udev.
This allows feedbackd to set periodic feedback and makes usable This allows feedbackd to set periodic feedback and makes usable
+2 -2
View File
@@ -96,13 +96,13 @@
recommended. recommended.
</para> </para>
<para> <para>
You can also acknoledge this with the definition option of your C compiler, like <literal>-DFEEDBACK_USE_UNSTABLE_API</literal>. You can also acknowledge this with the definition option of your C compiler, like <literal>-DFEEDBACK_USE_UNSTABLE_API</literal>.
This is required from Vala. This is required from Vala.
</para> </para>
<para> <para>
To use &package_name; from Vala, you must define the acknowledgment in C via <literal>-X -DFEEDBACK_USE_UNSTABLE_API</literal>. To use &package_name; from Vala, you must define the acknowledgment in C via <literal>-X -DFEEDBACK_USE_UNSTABLE_API</literal>.
If your build system uses a two pass compilation and hence your Vala compiler outputs C (Meson, Automake, or using the <literal>--ccode</literal> Vala compiler option trigger that) then you must add <literal>-DLIBFEEDBACK_USE_UNSTABLE_API</literal> to your C compiler argments instead. If your build system uses a two pass compilation and hence your Vala compiler outputs C (Meson, Automake, or using the <literal>--ccode</literal> Vala compiler option trigger that) then you must add <literal>-DLIBFEEDBACK_USE_UNSTABLE_API</literal> to your C compiler arguments instead.
</para> </para>
</simplesect> </simplesect>
+1 -1
View File
@@ -16,7 +16,7 @@ G_BEGIN_DECLS
/** /**
* LfbEventState: * LfbEventState:
* @LFB_EVENT_STATE_ERRORED: An error occured triggering feedbacks * @LFB_EVENT_STATE_ERRORED: An error occurred triggering feedbacks
* @LFB_EVENT_STATE_NONE: No state information yet * @LFB_EVENT_STATE_NONE: No state information yet
* @LFB_EVENT_STATE_RUNNING: The feedbacks for this event are currently running * @LFB_EVENT_STATE_RUNNING: The feedbacks for this event are currently running
* @LFB_EVENT_STATE_ENDED: All feedbacks for this event ended * @LFB_EVENT_STATE_ENDED: All feedbacks for this event ended
+1 -1
View File
@@ -103,7 +103,7 @@ fbd_feedback_led_run (FbdFeedbackBase *base)
FbdDevLeds *dev = fbd_feedback_manager_get_dev_leds (manager); FbdDevLeds *dev = fbd_feedback_manager_get_dev_leds (manager);
g_return_if_fail (FBD_IS_DEV_LEDS (dev)); g_return_if_fail (FBD_IS_DEV_LEDS (dev));
g_debug ("Periodic led feeedback: self->max_brightness, self->frequency"); g_debug ("Periodic led feedback: self->max_brightness, self->frequency");
/* FIXME: handle priority */ /* FIXME: handle priority */
fbd_dev_leds_start_periodic (dev, fbd_dev_leds_start_periodic (dev,