mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/504

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

** Bug watch added: github.com/Mudlet/Mudlet/issues #504
   https://github.com/Mudlet/Mudlet/issues/504

** Changed in: mudlet
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1639722

Title:
  Using the stopStopWatch( watchId ) does not stop the stop watch

Status in Mudlet:
  Opinion

Bug description:
  This has been an issue for a long time e.g. as mentioned in
  http://forums.mudlet.org/viewtopic.php?f=5&t=92&p=21102#p21102 - in
  fact the existing code does not behave as the Wiki
  http://wiki.mudlet.org/w/Manual:Mudlet_Object_Functions#stopStopWatch
  describes it {I recently added a warning about this}.

  The stopStopWatch(...) code is actually the same as the
  getStopWatch(...) code in the Host class and this breakage comes about
  because a QTime is used to record the "time" the stopwatch is
  "started" and it cannot be "stopped" - indeed there does not seem to
  be an existing Qt element that can be used "as a physical stopwatch as
  a user might understand it".

  I have assigned a "medium" importance to this as it ought to be fixed
  at some stage and it is broken as per the API described in the Wiki.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1639722/+subscriptions