mudlet-makers team mailing list archive

[Lynara Le'dominae <lynarasys@xxxxxxxxx>]

Precisely what sleep-deprived me was trying to communicate, poorly
On Jan 28, 2013 12:40 PM, "Eric Wallace" <1104487@xxxxxxxxxxxxxxxxxx> wrote:

> >From http://wiki.mudlet.org/w/Manual:Lua_Functions#stopStopWatch:
> "
> stopStopWatch( watchID )
>     Stops the stop watch and returns the elapsed time in milliseconds in
> form of 0.001. → createStopWatch()
>     Returns time as a number
> "
>
> Whether or not you agree with Lynara's statement that a stopped watch
> must start again from where it was stopped (which I do think would be
> the expected behavior of something called a stopwatch), it seems pretty
> clear that "stopping" it means that once stopped, subsequent requests
> for the time on the watch should return the time when it was stopped,
> rather than continuing to count up.
>
> --
> 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