Quote:
Originally Posted by juliansader
I like the idea of "whichever is smaller", since it would give the user much more liberty to determine the size of the active area: If snapping is enabled, the mouse would affect the CC or velocity in the same grid division. If snapping is disabled, the mouse would only affect the CC or velocity that is directly underneath the mouse.
If I am not mistaken, this is somewhat similar to how CC editing currently works, except that CCs' "active area" cannot go smaller than 1/8, and can go larger than 16 bar widths.
|
Honestly, it should just pick nearest to the pointer within range, from left or right regardless. And it doesn't have to calculate blocks vector, just pick from x axis position of the center point of cc block.