The max-hold function appears to not have any "memory", so it doesn't work the way you'd naturally expect such a function to work, where it simply keeps bumping up the "max" until reset. This implementation seems to have a very short "memory".
If there's some justification for such a behavior, it would be nice to be able to get the "usual"
behavior for "max/min hold".
The max-hold function appears to not have any "memory", so it doesn't work the way you'd naturally expect such a function to work, where it simply keeps bumping up the "max" until reset. This implementation seems to have a very short "memory".
If there's some justification for such a behavior, it would be nice to be able to get the "usual" behavior for "max/min hold".