what I’m interested in is a system that recognizes when there are heavy scenes and gives priority to setting the slider of the parameter that I want to set rather than start to lag to keep “realtime” the changes …
the condition that I would like to activate is always:
first move the parameter slider (in case of possible lag) and at the release of the click, assign the parameter to the object …
I hate terribly when it starts to lag. it makes my work from relaxing to hateful and nervous
edit:
studying your suggestion better seems a really comfortable solution compared to the current state … it could avoid making the work odious when it emerges lag …
The example you linked to has separate slider from amount input. Therefore a single click can have two different behaviors if you click in either. Still not sure how that would work in santbg’s example.
But you think about a cluster of properties like “Dimensions” in Properties. There is ResolutionX, ResolutionY, and “%” all together in a group.
All three of these will take a manual numerical entry and you can also drag your mouse to increase or decrease the value.
Are you suggesting that to manually enter a value with your keyboard that you single-click on two of these, but you need to (remember to) double-click on just one of them? Or are you suggesting that every property would need a double-click to enter a value rather than the current single-click?
double click avoids errors
and the one click “set a parameter between 0 and 1” is much more relaxing and immediate than being grab and drag every time …
So you are proposing that for all of our numerical inputs, where we can click once to enter value, should require a double-click instead?
Or are you saying that this is just for properties with a fixed range? So in my example above, IOR would be single-click while all the rest would be double-click?
I imagine for everywhere …
I’ve used this system in other software and I’ve always found it more immediate than being drag and grab each time to set a parameter …
notwithstanding that the drag and grab always remains when it is necessary, especially pressing shift to set more precise numerical parameters …
I’m not trying to be dick. I can certainly see the advantages.
There would obviously be no issues if the numerical entry was separate from the slider. But we are using the same area for both so there are conflicts that need to be thought through.
So let’s ignore for a moment the idea of requiring a double-click for all numerical inputs.
Instead think of an input that this would apply to. An input that goes from zero to one. Displayed in there right this moment is “0.15”. What happens at the moment you click that first click in the middle of that input? Does it change to “0.5” immediately because you clicked there? Or does nothing happen, just in case this is part of a double-click?
If that first click changes the value then that would mean double-clicking on the input would end up with you manually editing a value that is now 0.5. If you instead wait, in case it is going to be a double-click, that means you are delaying every single click action by the double-click time.
Again, not trying to be a dick, just pointing out some pitfalls with such a change to the current design.
