JohnnyReggae
Member
Th
That's kind of what I was thinking when I tried itUmm... I don't know, It looks cool?
That's kind of what I was thinking when I tried itUmm... I don't know, It looks cool?
Most of the time I keep my desktop display in portrait mode for work reasons (=less than 5/6 ratio). csTimer becomes all messy if I load it in portrait mode, have to rotate my screen back to landscape orientation before solves. Isn't there some more practical and more reliable way to recognize if the user is on a mobile device?I've just committed an update. There isn't any functional changes in this update. The only difference is some details of the interface, especially the adaption for mobile devices. Detailly, if you open cstimer on a screen whose width-to-height ratio less than 5/6, cstimer will switch to mobile version automatically.
Most of the time I keep my desktop display in portrait mode for work reasons (=less than 5/6 ratio). csTimer becomes all messy if I load it in portrait mode, have to rotate my screen back to landscape orientation before solves. Isn't there some more practical and more reliable way to recognize if the user is on a mobile device?
Most of the time I keep my desktop display in portrait mode for work reasons (=less than 5/6 ratio). csTimer becomes all messy if I load it in portrait mode, have to rotate my screen back to landscape orientation before solves. Isn't there some more practical and more reliable way to recognize if the user is on a mobile device?
update - Jul 20th 2016
Add color export and import function.
You may export/import the color theme to/from a string, e.g. "#000#efc#fdd#fbb#00f#ff0#000" .
In this way, you can share your color theme(s) with others.
The average of 5 1.009, rounded to just two decimals IS 1.01, I don't see anything wrong with that.Just noticed that when not using milliseconds, it still calculates averages with milliseconds. For example, if I put in five 1.009s, the average of 5 is 1.01. Any chance this could be fixed?
The average of 5 1.009, rounded to just two decimals IS 1.01, I don't see anything wrong with that.
You're right then! So, all those 1.009 should be already truncated to 1.00 and the avg should be 1.00 as well. Makes sense.The WCA truncates the third decimal, so if you're trying to be consistent with the WCA, then it should be 1.00.
Dude that sucks.I don't know if I'm the only one having this problem, but csTimer.net won't load on any of my devices! It's just a white screen, and never loads...