bkoelman / dogagilitycompetitionmanagement Goto Github PK

Should have good usage scenarios for them first, as we can only assign one additional function to these keys.

Also, maybe adding this obsoletes some other configurable sounds.

Related to #7.

Show run results grid (read-only) on MainForm (maybe hide state visualization on Release builds). Display two lists: one top-20 completed; one top-20 uncompleted.

Occasionally the network resync fails during a run (depending on how quickly it completed) when using the emulator. This is because the emulator does not properly implement the clock sync process. It should send a Notify Status (52) operation with 027:1 (Requires Sync) followed by Notify Status (52) operation with 027:2 (Sync Succeeded), but it only sends the last one. See comment here.

If unfinished (eliminated), clock keeps running. Should it be frozen? hidden? keep it running as-is?

Combine Network health display with NetworkGrid (the variant displayed on MainForm) and make it visually more appealing.

Possible errors to show, not specific to a device:

• not connected to mediator (possibly caused by protocol mismatch)
• mediator status nonzero (possibly unconfigured mediator)
• not compliant to class (typically: missing device in role XXX)

Possible errors that are device-specific: (maybe blink an error icon in front of device)

• misaligned sensor
• unsynchronized clock
• off-line (during run only)

Another approach would be to show all conditions needed for a run to start. Something like:

• Keypad: OK
• Start Timer: OK
• [ Intermediate Timer 1: OK ]
• [ Intermediate Timer 2: OK ]
• [ Intermediate Timer 3: OK ]
• Finish Timer: ERROR
• [ Delay between Start/Finish (single sensor): OK ]

where status value is one of:

• OK (Green check mark icon)
• WARNING (Orange triangle icon) - low battery / weak signal
• ERROR (Red cross icon) - device missing

Add support for showing intermediate time over existing time field. Hold intermediate time for a few seconds. Requires CIRCE support.

To be decided whether the holding is implemented in the displays itself or in the controller.

Requires additional background timers. EliminationTracker seems like a good place to implement this.

Requires changes to the expected outcome of truth tables in RunResultTotalOrdering specs

Extract common base class for NetworkGrid. Then have two derived classes:

• Display of what happens in the network (used in Setup Network dialog)
• Display of changes, based on active run composition. Do not add/remove devices, but color when device disappears

Related to #10.

To improve code quality. Examples:

• SonarLint
• CodeCracker
• RefactoringEssentials
• CSharpEssentials
• https://github.com/Pilchie/RoslynCancellationTokenAnalyzers

Also consider enabling allrules.ruleset once https://github.com/dotnet/roslyn-analyzers gets more stable.