Skip to content
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

When cycling back through the history, trigger point and channel are not updated #361

Open
mubes opened this issue May 28, 2021 · 3 comments

Comments

@mubes
Copy link
Contributor

mubes commented May 28, 2021

Steps to reproduce; Record waveform A using trigger x, Record waveform B using trigger y. Use history to go back to waveform A, trigger y is still displayed.

@azonenberg
Copy link
Collaborator

All scope settings (vertical scale, trigger configuration, etc) are displayed at their current values. Historical waveforms only store sample data, not a full snapshot of scope settings.

@602p
Copy link
Contributor

602p commented May 19, 2022

Having a snapshot of scope settings would be useful for me. We should maybe think generally about how to save scope setup information like this in historical waveforms. Function generator state will be another thing like this, since it would be nice to be able to e.g. characterize a filter at a range of inputs and save the whole thing as a .scopesession that includes the input func gen settings for each capture too.

This issue, #283, #343, #360 in my mind form kind of a feature bundle that would allow a scopesession to be "notebook-like" in containing labeled captures with their at-capture scope configs. Maybe open tracker ticket for that if that jives with your vision?

@azonenberg
Copy link
Collaborator

azonenberg commented May 19, 2022

Yes, I think that would be useful. Go ahead and file a ticket for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants