mudlet-makers team mailing list archive

[Lynara Le'dominae <lynarasys@xxxxxxxxx>]

API is not consistent, as has been pointed out. From the API:
*Stops the stop watch and returns the elapsed time in milliseconds in form
of 0.001

*
Stop something, and it is no longer running. It can be started again, and
it will start where it was stopped- for example, a vehicle stops, and
starts from the same position.

Correct API on this, as implemented, would read as such:
*Returns the elapsed time of the stop watch in milliseconds in form of 0.001

*
In short, if the implementation is correct, the wording in the API needs to
be reviewed so it is entirely consistent with the function's actual usage.

-- 
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