tangara-fw/src/tangara/input/input_volume_buttons.cpp, branch main Tangara firmware ailurux/button-media-controls (#264) 2025-03-19T04:25:20+00:00 ailurux ailurux@noreply.codeberg.org 2025-03-19T04:25:20+00:00 c9ce88a457c9ed7124709a667d202a666f72bffa Splits the control scheme into separate schemes for the side buttons and touchwheel, allowing them to be configured independently of each other. At least one input must be used for navigation, and there are guards to prevent locking oneself out of any input. If the input scheme is invalid, a pop up will show alerting the user. Different behaviours can be bound to the side buttons for when the device is locked or unlocked. This PR also adds a mode for these buttons that controls media playback (prev/next on up/down, pressing both buttons toggles play/pause). There are some changes to the way inputs handle locking. Rather than the input devices tracking the current locked mode, different input devices are created on lock depending on the mode that is configured. Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/264 Co-authored-by: ailurux <ailurux@noreply.codeberg.org> Co-committed-by: ailurux <ailurux@noreply.codeberg.org> 
Splits the control scheme into separate schemes for the side buttons and touchwheel, allowing them to be configured independently of each other. At least one input must be used for navigation, and there are guards to prevent locking oneself out of any input. If the input scheme is invalid, a pop up will show alerting the user.

Different behaviours can be bound to the side buttons for when the device is locked or unlocked. This PR also adds a mode for these buttons that controls media playback (prev/next on up/down, pressing both buttons toggles play/pause).

There are some changes to the way inputs handle locking. Rather than the input devices tracking the current locked mode, different input devices are created on lock depending on the mode that is configured.

Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/264
Co-authored-by: ailurux <ailurux@noreply.codeberg.org>
Co-committed-by: ailurux <ailurux@noreply.codeberg.org>
Add centre button haptic feedback on touch, and setting to disable/lessen haptics (#246) 2025-02-07T02:44:24+00:00 ailurux ailuruxx@gmail.com 2025-02-07T02:44:24+00:00 48495ddafe2ed59611c9491470f192b790e6146d This adds a way for feedback devices to respond to events from outside of LVGL's event system, being passed from input device to feedback device through a vector. This was done so that touch events and long-press triggers can now give feedback through haptics. This PR also adds haptic modes, saved in nvs similarly to input and locked input modes, to disable or change the haptic effect behaviour based on which mode is selected. Finally, this also fixes a bug in which some click events would not trigger haptics, at the expense of re-introducing the (undesired?) behaviour of clicking a button that transitions to a new screen causing a double click. Relevant issues this should close: #195, #233, and (partially?) #120 Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/246 Co-authored-by: ailurux <ailuruxx@gmail.com> Co-committed-by: ailurux <ailuruxx@gmail.com> 
This adds a way for feedback devices to respond to events from outside of LVGL's event system, being passed from input device to feedback device through a vector. This was done so that touch events and long-press triggers can now give feedback through haptics.

This PR also adds haptic modes, saved in nvs similarly to input and locked input modes, to disable or change the haptic effect behaviour based on which mode is selected.

Finally, this also fixes a bug in which some click events would not trigger haptics, at the expense of re-introducing the (undesired?) behaviour of clicking a button that transitions to a new screen causing a double click.

Relevant issues this should close: #195, #233, and (partially?) #120

Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/246
Co-authored-by: ailurux <ailuruxx@gmail.com>
Co-committed-by: ailurux <ailuruxx@gmail.com>
Add optional support for changing volume while locked 2025-02-02T04:48:42+00:00 Tess Eisenberger github@teisen.be 2025-02-02T00:15:17+00:00 1d485c97b0c03577a40b34fb762c76e98f417fa4 This adds a new Controls setting for adjusting the behavior when locked, and an option for allowing volume control. 
This adds a new Controls setting for adjusting the behavior
when locked, and an option for allowing volume control.
Add a new setting for input controls when locked 2025-02-02T04:48:42+00:00 Tess Eisenberger github@teisen.be 2025-02-01T23:59:08+00:00 e8eaf3df10a896cb28e91cfc416b19303926a00a This is just the plumbing of the new setting. The input methods will come in subsequent patches. 
This is just the plumbing of the new setting. The input methods will
come in subsequent patches.
Handle lock state in each input device, instead of in the lvgl driver 2025-01-15T04:37:35+00:00 jacqueline me@jacqueline.id.au 2025-01-15T04:37:35+00:00 a69b95187be4afce4eefa8f7b08ceca7b88b7724 






move driver includes into a subdir as well
2024-05-02T11:52:59+00:00

jacqueline
me@jacqueline.id.au

2024-05-02T11:52:59+00:00

26eb580043ad176bdc58d996f30d470e1073ef00












start moving include files into subdirs
2024-05-02T11:41:56+00:00

jacqueline
me@jacqueline.id.au

2024-05-02T11:41:56+00:00

7d7f7755d17e1e0a2348d75d797097f166b70471












WIP merge cyclically dependent components into one big component
2024-05-02T09:12:26+00:00

jacqueline
me@jacqueline.id.au

2024-05-02T09:12:26+00:00

1573a8c4cde1cd9528b422b2dcc598e37ffe94a7