Adds a debounce to the brightness slider to prevent laggy behavior. #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This feature adds a debounce mechanism to the brightness slider to prevent janky behavior when adjusting display brightness. Previously, every individual step of slider movement immediately triggered a DDCUtil call, causing rapid brightness changes and potential performance issues. Now, brightness changes are deferred until the user stops moving the slider (300ms delay), while linked sliders still update visually in real-time for immediate feedback.
What's changed
src/ui/screens/show_displays.c: Implemented debounce pattern using GLib'sg_timeout_add()andg_source_remove()_pending_brightness_timeout_idsand_pending_brightness_values) to track pending timeout IDs and brightness values per display_apply_debounced_brightness(): Handles the actual brightness application when the debounce timeout fires, including linked display support_update_display_brightness(): Changed from immediate brightness changes to scheduling debounced updatesHow to test locally
git checkout debounced-brightness-slider./build.sh./build/app