HP Forums

Full Version: [wp34s] Minor Issue with Stopwatch on real hardware
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

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

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.

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.

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.