Posts: 10
Threads: 3
Joined: Apr 2013
Hi all,
it seems to me, that if you press R/S to start and stop
the Stopwatch, the real calculator reacts about 100-200msec
delayed. The iOS or the QT Version do not show a markable
delay. I think that has something to do with key debouncing,
but I am still in an early stage of source code "reading" ;-)
Regards
Ralf
Posts: 225
Threads: 13
Joined: Jun 2011
Quote:
it seems to me, that if you press R/S to start and stop
the Stopwatch, the real calculator reacts about 100-200msec
delayed. The iOS or the QT Version do not show a markable
delay. I think that has something to do with key debouncing,
but I am still in an early stage of source code "reading" ;-)
Did you try comparing with a real stopwatch? I just did and it gave the same result as the WP34s to the tenth of second.
But the display may not give the impression of an immediate start on the real hardware though.
Posts: 10
Threads: 3
Joined: Apr 2013
Pascal,
you're right! Sometimes what you feel is not what you get :-)
I is just the display, that is delayed, but the measured
value is correct. I did the test with starting and stopping
the "realbuild" at the same time as the wife's iOS version and secondly
comparing it to the stopwatch of the son's Gshock ...
Thank you very much for that hint.
Cheers
Ralf
Edited: 16 Apr 2013, 4:11 p.m.
Posts: 2,309
Threads: 116
Joined: Jun 2005
I haven't looked at the 34s code.
The stopwatch code in the 41 Time Module and 41CX was carefully written to take keyboard scan and debounce time into account.