Special characters

[Deneb716]

Hi Roy, you might remember in our scoreboard when the time stops there's that little annoying third red dot inbetween the ":" and apparently this has a negative effect in reading the time properly, now as I am a complete novice in GitHub I don't know how is the correct way to do things but I'll provide a screeshot to see for yourself.

[royshil]

Thanks for the screenshot, it made this easy to track down! You're right: when the clock stops, the third dot in the middle of the colon means the OCR no longer sees a colon at all. It reads 2:36 as 236, and the Time box's Format (mm:ss) rejects that, so the outputs keep the last value until the clock runs again.

The next version fixes it. When a clock's reading comes back as digits only, ScoreSight puts the colon back where it was in the box's last good reading (2:38, then 236 is read as 2:36), as long as the result fits the box's Format. There's nothing to change on your side: once you update, the stopped clock will read correctly.

[royshil]

The fix is out in ScoreSight 0.4.3. When a stopped clock comes back as digits only (236), ScoreSight puts the colon back where it was in the box's last good reading (2:36), if the result fits the box's Format. There's nothing to set up. If a stopped clock still gets stuck after you update, a short recording of the board would help me track it down.

[Deneb716]

Because I'm using a bridge to connect Scoresight to an UNO overlay, the diagnostics have shown that imperfections on the reading when the third dot is on (and generally when the clocks ticks as normal) are drastically lowered which means that 0.4.3 handles, at least our clock, much better. I'm planning to use it on Saturday for our next home game, will report my experience after that match.