Hey qq,
I know this isn't a fault with csTimer, but I was wondering if there was anything you could do to csTimer to prevent instances like this from occuring.
To put it simply, there's something buggy with my QJ timer. It will connect fine to cs, but every now and then during a solve, it will, I guess "stop and start" the timer simultaneously. In other words, the timer will be ticking, then the csTimer menu and scramble and list times will all appear again for a split second before disappearing, at which point the timer continues to run as if nothing happened. It doesn't restart or anything. When I stop the timer that is my actual time. But I also have an extra incorrect time entered above the correct one, stating the time that the timer malfunctioned.
I don't know how something like this could be prevented. I did think of an implemented setting where the user would select a time that is uncommon for them, say 10 seconds. Then, if a solve time below the user chosen time is entered, the timer will ask the user for confirmation? Other than that I'm clueless.
All help from anyone is appreciated, if anybody has had the same issue and has fixed it by taking the timer apart, please let me know. Thanks