I've noticed that 10 is a more appropriate value for coarse integer adjustment. In fact, it's the increment value in the integer spinboxes when you press [CTRL] in the plugin properties window.
I'm not sure if it would be worthwhile to change in properties window to [SHIFT] instead of [CTRL] to maintain consistency with integer values in Direct Access.
However, for floating-point values, [CTRL] currently already works fine-tuning, just like in Direct Access.
It works great! Thanks!!!
I've noticed that 10 is a more appropriate value for coarse integer adjustment. In fact, it's the increment value in the integer spinboxes when you press [CTRL] in the plugin properties window.
I'm not sure if it would be worthwhile to change in properties window to [SHIFT] instead of [CTRL] to maintain consistency with integer values in Direct Access.
However, for floating-point values, [CTRL] currently already works fine-tuning, just like in Direct Access.
float fDelta = (pWheelEvent->angleDelta().y() < 0 ? -0.1f : +0.1f); if (pDirectAccessParam->isToggled()) fDelta *= 10.0f; else if (pDirectAccessParam->isInteger()) { const float fNumSteps = pDirectAccessObserver->maxValue() - pDirectAccessObserver->minValue(); fDelta *= (10.0f + fDelta) / fNumSteps; if ((fNumSteps > 10.0f) && (pWheelEvent->modifiers() & Qt::ShiftModifier)) { fDelta *= 10.0f; // <<<<<<<<<<<< Work better with 10 } } else { fDelta *= 0.5f; if (pWheelEvent->modifiers() & Qt::ControlModifier) fDelta *= 0.5f; } fValue = pDirectAccessObserver->valueFromScale( fScale + fDelta, bLogarithmic);