DalDal
Regular
I'll take a close look to see if I can find why this happened. It's difficult to replicate because it's rare though.I didn't do anything different form normal, this was maybe my 20th solve, and the others didn't have any bug.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

I'll take a close look to see if I can find why this happened. It's difficult to replicate because it's rare though.I didn't do anything different form normal, this was maybe my 20th solve, and the others didn't have any bug.
REALLY sorry, I'm aware of the issue and I'm releasing a new version very soon that will fix that.Doing some solves tonight on 2x2 and it seems to be putting the current scramble onto my previous solve's time. That is, solve #19 gets the scramble for solve #20 if 20 is the current scramble.
I understand the issue. Why do you use this feature in csTimer? Is there a specific set of times you want to go through or a scrambler that Block Keeper doesn't provide?I've been using Block Keeper as my main timer for a while now and I love it, but there's a bit of a problem:
On csTimer you can do one click (well click drag unclick) and you get the input scramble screen, then you can put in your scrambles and then it'll give them to you one by one, switching to the next one after every solve, then telling you once you've used them all.
In Block Keeper, you have to switch the scrambler to "Custom", and then paste all your scrambles in. But then it gives you all your scrambles in one big block so you have to manually keep track of which one you're on, and then when you're finished you have to manually switch back to "Recommended" or else every scramble for every event will be the big block of scrambles. I know you're a busy person, so when you have time could you try and fix this?
Ah I get it. Right now the scrambler system isn't really set up for keeping track of scrambles like csTimer does, where you can go next and previous. It's a bit out of scope for the next release, sorry.I mostly use it for race to sub-x threads, because those require use of specific scrambles
That's ok! I'm ok waitingAh I get it. Right now the scrambler system isn't really set up for keeping track of scrambles like csTimer does, where you can go next and previous. It's a bit out of scope for the next release, sorry.
- Changed record details menu to click rather than hover over
The reason I changed it is because I found it a bit unstable and easy to close when editing comments. Although it is a couple more steps, I think it is worthwhile. If you quickly want to change the result of the last time you can use Ctrl+1 2 or 3. You can also press ESC to close it quicker.Small request, could you make an option in settings to change this back to hover over?
Ok! The main reason I use this is because sometimes I forget that I have inspection time enabled so I start my solve before the timer starts, so I have to delete the time, but I found the command->Backspace hotkey on your guide so it's not an issue.The reason I changed it is because I found it a bit unstable and easy to close when editing comments. Although it is a couple more steps, I think it is worthwhile. If you quickly want to change the result of the last time you can use Ctrl+1 2 or 3. You can also press ESC to close it quicker.
Thanks you. I may have a workaround for the times that wouldn’t require a search function but I can’t test it now. Send me an email at [email protected] and I will help you in a couple of days so you won’t have to wait for the next version. Each time you change sessions, all the stats in the table need to be recalculated and displayed. If you have many many times it can take a while. I would recommend starting a new session regularly (maybe once a month) to keep the number down. Hope this helps.Thanks for the update, bugs are fixed
I have a request, could you add the possibility to search for a specific time ? The other day a friend used my timer and entered 5 sup20 times, which and now I need to find theses 5 times to delete them, in a session of 4.7k solves.
I also have a little problem, I like to have all of my solves in the same session, but when the session has more than 3k solves the timer begins to be really slow, it takes 10-30s to do an action in my 4.7k solves session (ex: switching session, show setting, show scramble, etc.) but the timer itself doesn't have this delay. Also when I'm on any other session that's less than 3k solves approximately it works just fine. Is there a way to fix this ?
Thanks a lot for your investment in this, this is by far the best timer and I recommend it to all my friends![]()
Feature request:
Add an option to disable start inspection using mouse (when inspection enabled)
My mouse timer sometimes will do weird things (directly start an inspection after stopping timer)
Also I think it is useful because a stackmat timer doesn't has inspection.
By the way, thanks for your hard work on this software.![]()
Sorry because my previous post is a bit confusing. Let me clarify:Thanks! The mouse timer starting weirdly is a bug and I'll look at fixing it. Also using a Stackmat is no reason not to have inspection, just another input type. You can ignore inspection using a Stackmat timer and use it normally, or start inspection.
To clarify my stackmat point. You use a stackmat in competition with inspection right? If you look at a stackmat as an input device rather than a standalone hardware timer, than it is indifferent to inspection. You could just start it or wait. A software timer emulates that competition inspection and you can have it or not by just starting or using a keyboard and mouse to start inspection. I think an option to specifically disable inspection while using a mouse it too specific, especially if a fix to make it more stable is made. thanksSorry because my previous post is a bit confusing. Let me clarify:
My request is add an option so that the mouse timer won't start inspection.
Reason:
1) Hardware problem-- inreliable mouse timer that will cause double clicks at the end of the solve (which I think no one care because it is my own problem) but just now you said it is software bug then ok
2) Actual stackmat doesn't have inspection (I doesn't meant to disable inspection on stackmat, just a reason because stackmat timer itself doesn't have inspection)
And also my request is add an option so everyone can choose the one that they like.
Thanks again!