Agreed, a totally customizable Smart tool would appear to be a potential solution, especially as there seems to be no consensus about what would be an optimum workflow but rather requests to make handling specific use cases easier at the expense of other use cases. However, making complex code customizable is a slippery slope, especially when you have something like the Smart tool that's embedded deeply into every corner of the program. I'm pretty sure the result would be a programming and QC nightmare. I would also not look forward to all the "SONAR
BROKEN!!!! SMART TOOLS SUCKS DONKEY BALLZ!! posts because someone didn't take the time to understand all the customization options.

You
know that would happen...
It's often better to offer different ways to do things rather than one customizable way, which in many cases is clearly the path Cakewalk has taken (e.g., three different ways to edit MIDI controllers, each optimized for a certain scenario).
But I appreciate that you offered a
specific suggestion so it can be evaluated. After thinking about it, unfortunately I believe there's a major problem with combining the Move tool with note entry.
With the Smart tool, after clicking to create the note, if you could then move it without lifting your finger off the mouse button you would
remove the option to edit the duration while holding the mouse button down, because holding the mouse button down would be dedicated to moving the note. I think that more users probably click where they want the note to occur, so they would find it much more useful to be able to edit the duration than move the note. It's not possible to assign a single mouse click or motion to multiple different tasks unless you use positional data to determine the function (which williamcopper hates, so he wouldn't like that) or use a modifier key to tell the mouse to use an alternate behavior (of course, some people complain about shortcuts...).
With the Draw tool, if you could click and then drag to change position, for similar reasons you would not be able to drag and create multiple notes at regular intervals with a single mouse motion. I don't know if Cakewalk has surveyed users as to which option they would prefer, but I create multiple notes with the Draw tool far more often than have a desire to change the note position once I've created it. I
suspect most users would feel the same way.
This is why I keep hammering on the fact that
specific, concrete proposals are needed to effect change. Sure, it's
possible to change the Smart tool functionality from "create note+edit note" to "create note+move note," but I suspect that would alienate 90% of the users in the process of pleasing 10% (if that).
No one from Cakewalk would
ever come in here and call users "stupid, dumb dumb wackos" because in their opinion those people weren't bright enough to figure out how to use the Smart tool optimally. It has nothing to do with smart or stupid. It is Cakewalk's task to
analyze the workflow of a large number of users, and come up with something that accommodates the majority. Just because a user doesn't like a particular programming tradeoff doesn't make them stupid any more than someone who loves a tradeoff makes them smart.
It's obvious Cakewalk is paying attention to what the community wants and implementing those wants as fast as they can. Many in the community have essentially partnered with the developers by providing reproducible steps for bug fixes. Implementing feature requests requires a well-thought-out proposal with a concrete solution that doesn't trade off commonly used functionality for less commonly used functionality. These things have to be thought through.
Also remember that SONAR can handle many different types of projects and is used by people who have very different workflows and needs. Using MIDI to create an orchestral piece, a drum machine beat, real time instrument part recording, editing hellishly giltchy MIDI guitar parts, or not using notes at all and creating control signals are
very different functions. Not everything can be customizable, for the reasons mentioned above. Therefore tradeoffs HAVE to be made. The object with software design is to have negative tradeoffs affect the minimum number of people and positive tradeoffs affect the maximum number of people. It is simply not possible to please all the people all the time, or provide an optimal workflow for
all workflows, given that many of these will be contradictory in their needs.