Being critical is just fine as long as you’re prepared to get challenged back. I’m way too stubborn to take that personally, but I have a genuine interest in what users really want and for what purpose (this is what I learn from). It is always better as I see it to first focus on what we want to achieve (irrespective of constraints) and for what purpose rather than how. This also has the added benefit of creating an arena where anyone’s opinion counts irrespective of specific competence or lack thereof. When the objective is clear, the how’s will come naturally.
The fact that a feature has limited application in one context does not rule out other uses. As such both fast mode and scan mode offer distinct values. It is my understanding that tobey is looking for a way to detect missing pulses and if that is the case we should probably be discussing pulse triggers rather than forcing a possibly inferior solution to this problem.
In terms of what you agree to, it is my understanding that tobey wants the exact opposite – a very fast real-time scan mode.
Provided we also shift the trigger position left, this makes sense and so I will look into this.