Skip to content

1193 set event time measurement precission - #1194

Open
fvacek wants to merge 17 commits into
mainfrom
1193-set-event-time-measurement-precission
Open

1193 set event time measurement precission#1194
fvacek wants to merge 17 commits into
mainfrom
1193-set-event-time-measurement-precission

Conversation

@fvacek

@fvacek fvacek commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

fvacek added 9 commits August 7, 2026 08:38
- Extend EventConfig with pointResults and pointResultsMaxPoints,
  default
  false and 1000, and load/save from variant maps; expose in UI.
- Introduce new QML reports: results_nstages_points.qml and
  results_nstages_points_condensed.qml.
- Extend RunsPlugin with:
  - nstagesClassPointResultsTable and nstagesPointResultsTable
  - stageResultsTable and currentStageResultsTable now accept max_points
  - propagate max_points to current stage reports
- Wire RunsWidget to expose menu actions for the new reports:
  "Points after n stages condensed" and "Points after n stages".
- Minor UI tweak: rename Event dialog group to pointResults
Remove obsolete commented-out results code and fix a typo in
disqualification handling.
Remove point-results enable toggle and radio sender tolerance settings.
Add configurable start and finish gate tolerances to event configuration
and use them when computing and displaying run times.
@fvacek fvacek linked an issue Aug 7, 2026 that may be closed by this pull request
@fvacek
fvacek marked this pull request as draft August 7, 2026 07:11
fvacek added 7 commits August 8, 2026 11:43
Register QML engine initializers and expose the default time
measurement precision to report JavaScript. Update OGTime formatting to
support configurable fractional seconds and adjust report column widths.
Reduce start-time column widths and format starter times to seconds.
@fvacek
fvacek marked this pull request as ready for review August 10, 2026 17:24
@fvacek
fvacek requested a review from arnost00 August 10, 2026 17:31
width: root.timeMsColumnWidth
halign: Frame.AlignRight
textFn: function() { return OGTime.msecToString_mmss(runnersDetail.rowData("timeMs"));}
textFn: function() { return OGTime.msecToString_mmss(runnersDetail.rowData("timeMs"));

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing } on line end.

@arnost00

Copy link
Copy Markdown
Collaborator

Time precision = 1 sec

2 runners same time (99.38), different position in print results :
obrazek

@arnost00

Copy link
Copy Markdown
Collaborator

Time precision = 1 sec

XML IOS v3 export :

<Result>
	<BibNumber>151</BibNumber>
	<StartTime>2026-08-06T13:55:00.661+02:00</StartTime>
	<FinishTime>2026-08-06T15:32:06.750+02:00</FinishTime>
	<Time>5826.089</Time>
	<TimeBehind>106.528</TimeBehind>
	<Position>2</Position>
	<Status>OK</Status>
	...
</Result>

Time & TimeBehind have different precision

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Set event time measurement precission

2 participants