If you stop a recording run in mid-stream, WS will try to rename the data file to be appropriate for however many sweeps were actually completed. If the target filename already exists, an exception gets thrown from Logging::stoppingOrAbortingRun(). This causes a dialog to be shown to the user, but WS never sets itself back to an idle state properly.
This is present 0.9192, and in commit 0e43052a6415946a4137bd92826619afa2256d59 on the develop branch.
This is another example of our need for some sort of framework for a short-term log of non-show-stopper warnings, which then get shown to the user (perhaps in summarized form if there are many of them) at the end of an operation.
If you stop a recording run in mid-stream, WS will try to rename the data file to be appropriate for however many sweeps were actually completed. If the target filename already exists, an exception gets thrown from Logging::stoppingOrAbortingRun(). This causes a dialog to be shown to the user, but WS never sets itself back to an idle state properly.
This is present 0.9192, and in commit 0e43052a6415946a4137bd92826619afa2256d59 on the develop branch.
This is another example of our need for some sort of framework for a short-term log of non-show-stopper warnings, which then get shown to the user (perhaps in summarized form if there are many of them) at the end of an operation.