- 20 Oct, 2021 5 commits
-
-
Guido Gunther authored
-
Guido Gunther authored
-
Guido Gunther authored
feedbackd Debian release 0.0.0+git20211018-1
-
Guido Gunther authored
-
Guido Gunther authored
We use these to lookup up the sound theme name
-
- 19 Oct, 2021 3 commits
-
-
Guido Gunther authored
-
Guido Gunther authored
feedbackd v0.0.0+git20211018
-
Guido Gunther authored
It was still stuck at 2021-10-07. Fixup version too while at that.
-
- 18 Oct, 2021 2 commits
-
-
Guido Gunther authored
-
Guido Gunther authored
Drop support for buster, this can be handled in downstream builds.
-
- 15 Oct, 2021 4 commits
-
-
Guido Gunther authored
Remove the feedback and the associated callback data before invoking the callback (which then triggers FbdFeebackBased:ended) since we otherwise remove the data from the currently playing sound from the hash table instead of removing the data from the sound that just finished playing. Call flow for a repeating sound before: on_sound_play_finished_callback() data->callback() fbd_feedback_get_ended() on_fb_ended() fbd_feedback_run() g_hash_table_insert(..., feedback, data) fbd_dev_sound_play() gsound_context_play_full() [async] g_hash_table_remove (..., data->feedback) <- removes wrong feedback So (since the feedback is still the same but only the callback data changes) we end up removing the data from the currently playing sound from the hash table and any calls to fbd_dev_sound_stop() would fail to find data and hence not cancel the playing sound. Call flow for a repeating sound now: on_sound_play_finished_callback() g_hash_table_remove (..., data->feedback) data->callback() fbd_feedback_get_ended() on_fb_ended() fbd_feedback_run() g_hash_table_insert(..., feedback, data) fbd_dev_sound_play() gsound_context_play_full() [async] So we remove the data of the currently playing sound before adding the feedback to the hash table again. No ownership is transfered to the hash table so no cleanusp need to be changed. Closes: #46
-
Guido Gunther authored
We name it `data` elsewhere. Don't call it `object` in one function.
-
Guido Gunther authored
The current name is just confusing
-
Pablo Correa Gómez authored
Fixes #45
-
- 14 Oct, 2021 1 commit
-
-
Pablo Correa Gómez authored
-
- 08 Oct, 2021 5 commits
-
-
-
-
Named after the corresponding notification from the sound naming spec: http://0pointer.de/public/sound-naming-spec.html
-
Named after the corresponding notification from the sound naming spec: http://0pointer.de/public/sound-naming-spec.html
-
Named after the corresponding notification from the sound naming spec: http://0pointer.de/public/sound-naming-spec.html
-
- 07 Oct, 2021 1 commit
-
-
Evangelos Ribeiro Tzaras authored
This will make sure that the json theme file gets validated in CI.
-
- 22 Sep, 2021 1 commit
-
-
Arnaud Ferraris authored
-
- 06 Sep, 2021 1 commit
-
-
Guido Gunther authored
-
- 09 Aug, 2021 2 commits
-
-
Guido Gunther authored
For that we must not set a default event.
-
Guido Gunther authored
It's '-P', not '-p'.
-
- 23 Jul, 2021 4 commits
-
-
Guido Gunther authored
The method is `trigger_feedback` not `trigger`.
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
Phosh recently changed to XDG_CURRENT_DESKTOP=GNOME:Phosh and has since stopped using the configured theme and instead used the fallback freedesktop theme. Closes #41
-
- 08 Jun, 2021 1 commit
-
-
Pablo Correa Gómez authored
This would allow users to create their own feedback profiles without editing system files or using root privileges Signed-off-by:
Pablo Correa Gómez <ablocorrea@hotmail.com>
-
- 31 May, 2021 2 commits
-
-
Andreas Hartmann authored
The README currently states that feedbackd uses the `default.json` theme, whose location is hardcoded into the application. This doesn't reflect the current state of the code. Explain the ability to add custom themes and give some examples to the user. Also mention the `feedbackd-device-themes` repository explicitly for users looking to modify the current `default.json` theme. Adds explanations about the correct naming of custom theme files and theme file precedence when multiple themes exist.
-
Andreas Hartmann authored
Previously, assembly of the theme paths for custom paths (based on `XDG_DATA_DIRS`) was performed using `g_strconcat`, which produced erroneous file paths with missing path separators due to a typo in the code. Instead, make use of `g_build_filename` to assemble the theme paths from `XDG_DATA_DIRS` to look for custom themes, which automatically introduces host-specific path separators between individual path components. This introduces another temporary variable to ensure that the filename (which is itself assembled from a name and the file ending) isn't mangled by introduction of a path separator between these two "parts".
-
- 04 May, 2021 1 commit
-
-
Evangelos Ribeiro Tzaras authored
-
- 27 Apr, 2021 6 commits
-
-
Guido Gunther authored
-
Guido Gunther authored
-
Guido Gunther authored
-
Guido Günther authored
Update to 0.0.0+git20210426 See merge request DebianOnMobile-team/feedbackd!6
-
Guido Gunther authored
-
Guido Gunther authored
Update to upstream version '0.0.0+git20210426' with Debian dir ce67e973f713e33c09e66e1871ba0e0c60111e2c
-
- 26 Apr, 2021 1 commit
-
-
Guido Gunther authored
-