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

Bug #1639722 reported by Stephen Lyons on 2016-11-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mudlet
In Progress
Medium
Stephen Lyons

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.

Vadim Peretokin (vperetokin) wrote :

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.

Changed in mudlet:
status: New → Opinion
Stephen Lyons (slysven) on 2019-04-22
Changed in mudlet:
assignee: nobody → Stephen Lyons (slysven)
status: Opinion → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.