Taking away features is a sure way to piss off your user base. That's exactly what Cakewalk has done w/ drawing tool customizations.
 
We've had some discussion here about changes people would like to see to behavior of the tools on the tool palette. Of course this is something users will never agree on. But prior to the X series it was possible to define custom tool actions, so every user could have the tools do what they wanted. For example I had the select tool + the control key mapped to velocity so I could easily adjust MIDI note velocities w/o having to faff around w/ the mouse trying to catch the top pixels of the note.
 
But custom tool mappings have been taken away and so we're stuck w/ the actions Cakewalk has defined for the tool palette. Please vote if you would like to see custom draw tool mappings brought back.

What I have done is the following.  Create two Cals. One to increment selected velocities by one and the other to decrement velocities by one. I named these cal files "Velocity up.cal and "Velocity down.cal" respectively and placed them in the cal folder.  You can find this folder by checking your "folder locations" settings.  While probably not an eligant solution, but it works for me..

Then I mapped one key combination (SHIFT PAGE-UP) to "Velocity up.cal and another (SHIFT PAGE-DOWN) to "Velocity down.cal"
 
Here are the respective cals
-
Velocity up.cal
_________________________________________________________
(forEachEvent
    (if (&& (== Event.Kind NOTE) (< Note.Vel 127))   
        (do
            (+= Note.Vel 1)
        )
    )
)
_________________________________________________________
 
Velocity down.cal
_________________________________________________________
(forEachEvent
    (if (&& (== Event.Kind NOTE) (>= Note.Vel 1))   
        (do
            (-= Note.Vel 1)
        )
    )
)
_________________________________________________________

Meh. Much easier to click-drag notes on the fly. In any case velocity is just an example. What I am requesting is the return of custom mappings for the tool palette. Another example is everyone would like to change the freehand tool's behavior on existing notes from "glue" to something actually useful -- but what? Erase? Move? It should be customizable so users can choose their own preference. 

promidi
What I have done is the following.  Create two Cals. One to increment selected velocities by one and the other to decrement velocities by one. I named these cal files "Velocity up.cal and "Velocity down.cal" respectively and placed them in the cal folder.  You can find this folder by checking your "folder locations" settings.  While probably not an eligant solution, but it works for me..

Then I mapped one key combination (SHIFT PAGE-UP) to "Velocity up.cal and another (SHIFT PAGE-DOWN) to "Velocity down.cal"
 
Here are the respective cals
-
Velocity up.cal
_________________________________________________________
(forEachEvent
   (if (&& (== Event.Kind NOTE) (< Note.Vel 127))   
       (do
           (+= Note.Vel 1)
       )
   )
)
_________________________________________________________
 
Velocity down.cal
_________________________________________________________
(forEachEvent
   (if (&& (== Event.Kind NOTE) (>= Note.Vel 1))   
       (do
           (-= Note.Vel 1)
       )
   )
)
_________________________________________________________

Nice! Very useful. Thank you.

What do you think guys, is it possible that Cakewalk admit their evident mistake after so many years, and so many user requests, and return it back in some way?

Adq
What do you think guys, is it possible that Cakewalk admit their evident mistake after so many years, and so many user requests, and return it back in some way?

Hope so!

Yes indeed.  I inevitably refer to the smart tool as the dumb tool, since it can't be configured to do what I want it to do.   Voted.

bump