played around a bit with SCDoc this afternoon and found a number of issues, some of them quite disturbing (SC 3.10.0, 3.10.1, 3.10.2 on OS 10.13.8).
I start with the most serious first: selecting a region within parenthesis by double-click inside the parenthesis and then evaluating it leads to a double evaluation! It doesn’t only happen with double-click, selecting some lines with the cursor and then evaluating them produces the same error.
If this is a general problem on OSX (and not only a strange problem of my setup) it would be really bad, beacause hundreds of help file examples are concerned. Even worse: for many especially new users it would be nearly impossible to realize, examples just produce wrong/blurred audio !
By evaluating with moving the cursor inside a parenthesis and pressing Cmd-Return the double evaluation sometimes doesn’t happen for many times, then again it happens all the time.
Then there are cases where Cmd-Return doesn’t select a region for whatever reason (I don’t have a good reproducer for this at hand but will investigate further), and then automatically one has to apply another selection/evaluation way, which always produces double evaluation.
Admittedly: I would have noticed that earlier probably if I had more often worked with 3.10 during the last months, but there’s a reason why I didn’t: for many years it was possible to use different version of SC on the same computer without any problems, I mean not at the same time but using the same Extensions folder. With 3.10 and 3.9 a switch causes problems, e.g. if you go back from 3.9 to 3.10 the code of all help files has disappeared!
To repair this, the only workaround I found was deleting the Help folder inside Extensions and restart 3.10. So ironically more backward compatibility in this regard would have motivated me more to test the new versions …
That all should not sound like a big complain. Developers are doing serious and gorgeous work and bugs can always happen. But the help system is like a visiting card of a software. If the most basic thing, evaluation of example code, is such a pain, we should think about repairing this.