I would export all my times to a file and to the server and then remove all cookies and then import everything again. Make sure the exporting went OK before you delete cookies!This just started happening today. My times get deleted but only to a certain point, solve 1352, whenever I leave the website, or switch sessions. I would do an average then switch to another event, and my times after solve 1352 are gone. I've never seen this before. Please help!
I double checked the site, my session names are still the same and I have not cleared the cookies.Did you maybe clear your cookies?
Are you on the same cstimer url you were before? - https://cstimer.net - https://www.cstimer.net <- those save independently.
If you didn't do any backups and the times are really gone - they're gone. Be sure to make backups in the future, after logging in via WCA id or your google account it's just 2 clicks away.
is not a good way. Not a nice tone, very few and not very unambiguous information. If I was a dev, it could be that I'd ignore a comment like yours.ok so all my times got deleted???
Thanks for the advice, I'l keep this in mind Yes you've got the summary right more or lessSo only your times are gone, sessions and all your options are still there? And the times in all of your sessions are gone? If it was just one session, I'd guessed you maybe accidentally deleted them (alt+d + enter clears all the times in one session), but if all times in all sessions are gone that's pretty unlikely to happen accidentally. When you do a solve now, does it show in the list? Is the solve number for the first new solve 1 or is there maybe an error that it just doesn't show previous solves?
I lack the knowledge to really help you, but if you didn't clear your cookes, maybe the developer can, if it's really a bug. You can try to open an issue on github, if he doesn't answer here.
Just a tip for the future - if you make a bug report and/or want help (in general, not necessarily cubing related):
Try to give as much useful information as you can and try to be very specific.
is not a good way. Not a nice tone, very few and not very unambiguous information. If I was a dev, it could be that I'd ignore a comment like yours.
The signal-report rate from stackmat timer is too low, which is only about 7~8 signals/second. When you put your hand on the pad, cstimer will get this information about 0.15 seconds later. Furthermore, if you just touch the pad instead of keeping your hand on the pad, stackmat timer may not transfer the touch information at all.I think I've suggested some things here before and they've been implemented so let's try this
I am aware of a feature that allows for use of a stackmat timer to begin the inspection timer by tapping the right pad of the timer. Is this kind of signal relay-able mid solve? If so, would it be possible to implement a similar feature where tapping the right pad can be used to record splits for a multi-phase session?