mirror of
https://github.com/IAmTomShaw/f1-race-replay.git
synced 2026-05-09 08:25:56 +02:00
[PR #142] [MERGED] Fix button click behavior and implement interactive hold-to-seek logic #171
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/f1-race-replay#171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/IAmTomShaw/f1-race-replay/pull/142
Author: @MananJK
Created: 12/30/2025
Status: ✅ Merged
Merged: 1/10/2026
Merged by: @IAmTomShaw
Base:
main← Head:button-updations📝 Commits (4)
231e448Made changes to the button behaviourd48a00eMerge branch 'main' into button-updationsdce5c92Fixed timelapse speed bug2055706Add missing multiplier for seek speed in qualifying📊 Changes
3 files changed (+95 additions, -26 deletions)
View changed files
📝
src/interfaces/qualifying.py(+41 -12)📝
src/interfaces/race_replay.py(+35 -5)📝
src/ui_components.py(+19 -9)📄 Description
Identified and fixed a bug where users had to repeatedly click the arrow keys to seek to a specific time during the race. I implemented a button hold-down feature for both the keyboard arrow keys and the on-screen mouse buttons.
When held, the race pauses and seeks (rewind/forward) continuously. The playback state is maintained for the duration of the action; when the button is released, the race resumes automatically. If the user had already paused the race manually beforehand, that state is respected and the race remains paused after the seek action.
Changes:
https://github.com/user-attachments/assets/71e14e46-6a72-4123-8483-5b6514a5d10e
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.