Opened 16 years ago
Last modified 16 years ago
#125 assigned defect
Lap count on the LapView isn't immediately updated — at Version 5
| Reported by: | Florian Roth | Owned by: | nobody |
|---|---|---|---|
| Priority: | critical | Milestone: | MS4: Future extensions |
| Component: | track | Version: | pre-1.0 |
| Keywords: | Cc: |
Description (last modified by )
The lap counter in the LapView sometimes lags behind reality (and the simulation). The events are fired, but apparently the table in the LapView isn't immediately updated or at least not redrawn.
This seems to be more noticable on slower computers, which might indicate that it has something to do with the processing of the event loop. Lags of up to multiple seconds have been spotted.
Change History (6)
comment:1 Changed 16 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 16 years ago by
| Summary: | Test the LabsView → LapView shows incorrect lap count |
|---|
Changed 16 years ago by
| Attachment: | LapView-Problem Patch.patch added |
|---|
comment:3 Changed 16 years ago by
| Owner: | changed from Fabian Rohn to Henrik Heimbuerger |
|---|
comment:4 Changed 16 years ago by
New commit by hheimbuerger (revision [411]):
[Partial fix for ticket #125, related to ticket #53] Redraws are no longer triggered if the TrackWidget isn't already idle.
Before pushing a new redraw event to the event queue, the TrackWidget now checks whether it's already working on a frame. That should reduce the problem of the refresh events for the LapView not getting through. (In the latest tests, it still took up to 2s, unfortunately.)
The dropped frames are shown on the frame counter.
comment:5 Changed 16 years ago by
| Description: | modified (diff) |
|---|---|
| Milestone: | MS1: First usable version → MS5: Optional extensions |
| Owner: | changed from Henrik Heimbuerger to nobody |
| Summary: | LapView shows incorrect lap count → Lap count on the LapView isn't immediately updated |
experimental fix