and this actually does not matter, you talk about 30 vs 4 waveframes per second. Both values are such
low that you can't use these scopes (in this particular memory depth setting) to catch any kind of glitches.
This all is about human perception. I personally feel more comfortable if the waveform on the display reacts smoothly to my commands. I hope it will be possible to emulate analog scope look and feel in the Hantek custom firmware.
i remember there was version working bit faster, something about 16 frames/s while in 1M mode. That was already
acceptable (from UI point of view), the lag was under 100ms.
In principle the idea of having keyboard control in FPGA was ok, there is no lag internaly.
The problem is on ARM side, afaik the process will be not interrupted on keyboard change. From a data integritiy point of view
a good idea, the last thing you wish is inconsistent data because of broken thread after interrupt.
For sure this can be done better, the only open question is how fast such firmware will be. I've played with current firmware,
e.g. patched the key event procedure to call an init after key status change - the resulting lag was samller, however due
missing event filter the fw was doing init after every change, so not the best idea.
On the other side they working on the firmware, the progress (of bug fixing and improvements) was already very good
(see fw 2.06.3_120625.0), let's hope they still on track. I think i will ask for updates on that.