Public bug reported:
• If you createStopWatch, then immediately getStopWatchTime, it has an
unbelieveably high time - this time should be a stable 0, not an increasing
time.
• stopStopWatch does not actually stop the watch, it only returns the current
time. This should stop the watch, so that the stopwatch can be restarted from
the time it was stopped at.
• startStopWatch always resets it to 0, instead of just starting it where it
was left off before. This is a moot point until stopStopWatch is fixed
• resetStopWatch() should reset the stopwatch to 0, not to the increasingly
high number it was showing when createStopWatch was called.
** Affects: mudlet
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1104487
Title:
stopwatches have a number of bugs, as listed
Status in Mudlet the MUD client:
New
Bug description:
• If you createStopWatch, then immediately getStopWatchTime, it has an
unbelieveably high time - this time should be a stable 0, not an increasing
time.
• stopStopWatch does not actually stop the watch, it only returns the current
time. This should stop the watch, so that the stopwatch can be restarted from
the time it was stopped at.
• startStopWatch always resets it to 0, instead of just starting it where it
was left off before. This is a moot point until stopStopWatch is fixed
• resetStopWatch() should reset the stopwatch to 0, not to the increasingly
high number it was showing when createStopWatch was called.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1104487/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mudlet-makers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~mudlet-makers
More help : https://help.launchpad.net/ListHelp
