I remember when Autodesk announced their major "Small Annoying Things" 3dsmax campaign, where after years of angry commenting from customers they finally understood that we wanted all those small but workflow-slowing bugs, weirdnesses, or lack of vital tools to be fixed/implemented. They held various user group meetings with their department head(s) (I was at one in London) to actually get this feedback 1:1. It never quite hit the mark fully but it was a great period and had a very noticeably positive impact on 3dsmax, and I think the attitude has carried forward there ever since. Naturally, the issue nowadays over there is a massive lack of innovation within 3dsmax, so it could certainly be fairly argued it's gone too far the other way!
Anyway, it's something to think about. I've often wondered if Corona development would be better handled by making existing-feature improvements, bug fixes just like this happen to point version updates/hotfixes e.g. 12.1, 12.2 etc. and saving the new feature updates for major versions (and not necessarily every major version). In that way perhaps it would be possible to delay major new features being worked on and pivot development to addressing sometimes very serious bugs within the current major version in a hotfix - as many as needed - maybe 2, 3 or 4 x. In recent times there have been instances where potentially show-stopping bugs have had to be left for some future major version update because it's too late to shoehorn it in, causing frustration in the userbase (reasonably so...). As a studio, we have completely skipped 2 or 3 major versions of Corona (maybe 8, definitely 12) because of this situation. And if that reminds anyone of how many of us work with 3dsmax then I'm not surprised! Since 3ds max 2008 or so we have ignored every other version, because it's pretty well-known that the odd-versions are usually where the bulk of new features are introduced, and the even version is where they're bug-fixed and optimised... in a production environment that's critical stuff.... We don't and can't work with flakey software. C12 has proven a bit of a nightmare judging by many accounts on this forum, so we've skipped it. Not something we want to have to do, ever.
