Got it. We can assign middle click + drag to this functionality. Currently, dragging horizontally with either the left or the middle mouse button do the same thing.
Figuring out if the user is trying to interact with a specific waveform based on mouse position is error-prone (especially in point mode).
I was thinking the user would click on far right area to select the waveform they want to work with. Maybe change the box thickness or some other way to graphically denote it is the selected waveform. Then just drag away.
Indeed playing with CDF settings will improve sweep rates, but at a cost. Shown with 202020.
There does appear to be some strange interaction with the CDF settings and trigger that I could never explain. I can reproduce it on this end and it has worked this way for some time. I'll try and walk you through what I see using the Tektronixs pulser.
Power up unit using defaults. Set the trigger level to 500mV. Set the position to center the waveform (86ish ps). Set the Base to 20ps/div. Set resolution to 128 pts/div. Set the holdoff to 150ns. Sweeping should be very slow (>10 minutes). Next select the CDF sampling options and use your 202020 settings and apply. Change the resolution to 4 pts/div, sweep is maybe 2 seconds.
Now the fun part, change the CDF sampling options back to auto and apply. Now, select a resolution of 128 pts/div. This should get us back to the initial state but the sweep rates will be much faster. Here is the trick. Set the trigger level to 100mV. Now change it back to 500mV. If all is right, I am expecting it to again sweep very slowly as it did in the start. Now why this trigger level being set to something else and then returned to the initial value has any effect on the sweep time, you would need to chime in. I'm sure it's a user problem and some misunderstanding I have. Guessing the settings are not critical as I have ran into this before. The order does not seem to matter. Nor does changing the holdoff. It seems tied to having to change the trigger level. Like the act of doing that is somehow causing some state of the software to change.
If this is too confusing to follow (I take no offense to that
), I can make a small video for you demonstrating what I am seeing.
*******
It appears that when selecting the "Automatically determine from holdoff" the software does not immediately calculate the new values. Rather is seems to require some event such as changing the trigger level or the holdoff time. Maybe this is by design but personally, I would rather it calculate the new values based on the current settings instead of having to change values to get it update.
*******
Also, if I load settings that do not have the CDF settings set to auto, they will take effect immediately. If I then load settings that use auto for the CDF, the software does not appear to update to the correct values. Lots of clues.