Brief summary of issue / Description of requested feature:
So I'm just starting to see how many issues are caused by the updated stopwatch functions. Alot of scripts at least that I use don't pass the name of the stopwatch as a string so I get all kinds of errors about invalid arg due to expecting a string or a number. The biggest noticeable issue I found at first was it immediately broke the mapper as it relies on stopwatches to speedwalk anywhere.
Steps to reproduce the issue / Reasons for adding feature:
As far as reproducing, just try to speed walk with the current release of the mapper and you can see it doesn't know what to do and errors out. There are several instances within svof that also pass variables to the stopwatch args as well. This is very early on analysis, bear in mind, just wanted to bring it up.
Brief summary of issue / Description of requested feature:
So I'm just starting to see how many issues are caused by the updated stopwatch functions. Alot of scripts at least that I use don't pass the name of the stopwatch as a string so I get all kinds of errors about invalid arg due to expecting a string or a number. The biggest noticeable issue I found at first was it immediately broke the mapper as it relies on stopwatches to speedwalk anywhere.
Steps to reproduce the issue / Reasons for adding feature:
As far as reproducing, just try to speed walk with the current release of the mapper and you can see it doesn't know what to do and errors out. There are several instances within svof that also pass variables to the stopwatch args as well. This is very early on analysis, bear in mind, just wanted to bring it up.