Feature suggestion, Servo test mode

Here's an example of an experimental 'delay' mixer I quickly coded up:



The mixer is a type (like replace, add, min, max) so it is only available as a 'Complex' mixer. It compares the Source to the calculated value (after applying scalar and curves) and then uses the offset as the 'speed' value. I need to think of a better way to do it, ideally without adding yet another variable to the mixer structure, but this shows that it is possible to code it into the mixer as we've discussed.

I have an implementation I'm happy with now.
When you set the mux-type to 'delay' the curve actually represents time for the servo to go from 0-100%.
So the typical use would be to have the 1st mixer define the expected value, and the 2nd mixer to apply a delay using a 'fixed' curve type (using 'scalar' to define the amount of delay). you could have non-linear delay as well if you are so inclined.

The question I have is how slow should it be?
typical servos can complete a 0-100% sweep in 0.1 to 0.2 seconds.
We have a total of 100 steps available.
Currently I am using 1 step = 0.1 second. So on a 0.1s servo, a value of '1' would have no effect, a value of '2' would be half speed, a value of '10' would take 1 second to go from 0-100%, and a value of '100' would take 10 seconds to go from 0-100%

There are other algorithms, but this one seems to make the most sense to me, so the question is really: What is the finest granularity you want control at? Is 1/10sec fine enough for 0-100% or should we go finer (at the cost of the slowest sweep)?

I think that will be overkill. I've set it to 5sec 0-100. This looks like it will cover all uses (fyi, I believe the most common usage is actually for landing gear with a standard servo).

I have checked in support for slow mixers now. Here is a example that shows a channel sweep using 1 virtual channel (3 mixers) and the output channel (2 mixers) There may be even better solutions, but this showcases the new capabilities.

FYI, I will likely remove support for the limits-based speed before the next release

Works fine for me in 0f23fad098e0