mudlet-makers team mailing list archive

[Lynara Le'dominae <lynarasys@xxxxxxxxx>]

How is this a 'neither' - they do the same thing as implemented. By
definition, as implemented one is redundant. This would not be so if they
did different things... but they don't. Can you explain the difference
between the two, if there is one?


On Sun, Jan 27, 2013 at 5:11 PM, Vadim Peretokin <vperetokin@xxxxxxxxx>wrote:

> Neither. The implementation is not relevant to the API it offers. It is
> intended this way.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

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