Hi:
I noticed when using SETTIM that the input argument's seconds value seems to be ignored and replaced with some value between 10 and 14.
For example if I have 22.0400 on the stack, execute SETTIM then immediately press hTIME I get a value back of 22.0412 instead of an expected 22.0402 or something close to that.
Regards,
Bob
Wow! A command all for me. :-)
Tim W
Oh man, I hope that's not changing your TV channels or something :-)
I will check it. What happens, if you set the clock to something like 1.2345 ?
Edit: The seconds written to the RTC were definitely bogus. I fixed it in SVN for V.1.8. V1.17 will not be fixed.
Edited: 18 May 2011, 3:37 a.m.
Just installed 1.18 - problem solved.
Thank you!
Bob
Edited: 18 May 2011, 10:04 p.m.
Aren't you glad there's no KILLTIM command? ;-)
Regards,
John
Come on, that was a peaceful project so far :-)
Walter
Other possibilities: PEEKTIM, POKETIM, PUTTIM, POPTIM, PUSHTIM, DIVIDETIM, ROTATETIM, FLOATTIM, MASKTIM, ABORTTIM...
Let's hope your wife doesn't execute REMOVETIM, SWAPTIM or REPLACETIM.
John