-
|
I'm so used to hitting tab right after a test, that when i get a new best, i subconsciously tab it away, and can't screenshot the screen. It would be nice if you could add an option that doesen't let you tab for 3/5s after a new best. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
Sure, why not, i can add a 3 second block EDIT: Well, looking into this now, I don't know if a result is a pb until a response comes back form the server. The local data is not guaranteed to be 100% correct, so i just wait for the response. And then blocking the test restarting until the response arrives is also not the best UX, since the requests could get delayed. Not sure whats the best thing to do here. |
Beta Was this translation helpful? Give feedback.
-
|
okay, what if you allowed downloading the screenshot (like you do in the result screen) for the last 3/5 results? I know the screenshot thingy relies on the html elements being present and using something like html2canvas (i assume). Only thing that might be a problem is if the server does not store all the data like speed graph for past results. |
Beta Was this translation helpful? Give feedback.
-
|
All the data is already available on the account page, and you can view the graph by clicking the graph icon |
Beta Was this translation helpful? Give feedback.
-
|
yeye but i want that sweet new best screenshot i forgot to take by tapping tab too fast |
Beta Was this translation helpful? Give feedback.
-
|
Or you could... you know... not press tab as soon as possible? |
Beta Was this translation helpful? Give feedback.
-
|
it's hard coded in my muscle memory lol. yes i know it's my skill issue but 3s block is easier to implement that rewrite muscle memory i think |
Beta Was this translation helpful? Give feedback.
Sure, why not, i can add a 3 second block
EDIT: Well, looking into this now, I don't know if a result is a pb until a response comes back form the server. The local data is not guaranteed to be 100% correct, so i just wait for the response. And then blocking the test restarting until the response arrives is also not the best UX, since the requests could get delayed. Not sure whats the best thing to do here.