-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to decouple changing the Y axis from changing the Y axis settings on the scope #106
Comments
(Note this is written from my point of view, it's not an assumed point of view for the majority) Summary of a discussion elsewhere:
The vertical controls could be decoupled from the display control. Added benefit: having hardware control decoupled from display control becomes even more relevant for 12-bit scopes where it might be easier to capture the full height of a waveform, then zoom into a feature of interest. Following on from that:
|
Some discussion of this in Discord when I tripped over this today. I agree that X and Y behaving differently is definitely an 'at least one of them is wrong' situation. One idea I am toying with is that a waveform view should, metaphorically, represent a capture of a state of the system, and might have indications for 'these were the parameters this capture happened with', and also indications for 'these parameters are what will apply to the next capture'. Consider, for instance:
|
Right now, when you change the Y axis in glscopeclient, these changes get transmitted to the oscilloscope.
This is not always desired: you may want to zoom in on an acquired signal without changing the settings of the scope.
There should be an option to do that.
The text was updated successfully, but these errors were encountered: