Performance Optimization and Activity History Feature#16
Conversation
- Added `update_stats_batch` to `DataStore` for atomic SQLite updates. - Refactored `StatsDialog` with `QTabWidget` and added "History" tab. - Implemented `log_event` calls across the app for key interactions. - Optimized `InputManager.flush_all` to use the new batch method. - Verified changes with automated tests and UI screenshots.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This update focuses on both performance optimization and feature completeness.
Performance (Data Layer): Introduced
update_stats_batchinDataStoreto perform all statistics updates (bonding points, KPS, clicks, etc.) in a single SQLite transaction. This significantly reduces I/O overhead during theflush_allprocess inInputManager.Feature (Activity History): Upgraded the
StatsDialogto a tabbed interface.activity_logtable.Logging: Added descriptive
log_eventcalls inInputManagerandTrayMenuto populate the activity history with meaningful data.Tested with
unittestand verified visually via offscreen rendering screenshots for both "Progress" and "History" tabs.PR created automatically by Jules for task 2718385397371333976 started by @mx57