You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working on an issue that has demanded incremental changes in an attempt to understand both the documentation and peripheral.
I've found that I would really like to be able to do two things with the historical waveforms:
Pin a Waveform.
This would allow us to make a capture and keep it in the history - currently old waveforms will be discarded to maintain the configured maximum. Behind the scenes, this could be implemented as a separate queue, or it could be implemented by allowing "pinned" waveforms to bubble to the top and then persist. I'm happy (and able) to configure quite a large history (>100 wfms), so I'm okay with the latter, but others may prefer the former.
Label / Name a Waveform.
In the workflow I've outlined, this would permit a textual name to be associated with the waveform. For example, register values that produced the given waveform. The timestamp is still useful, so I'd suggest presenting this along-side the timestamp.
I've included a nasty mockup below:
The text was updated successfully, but these errors were encountered:
I've been working on an issue that has demanded incremental changes in an attempt to understand both the documentation and peripheral.
I've found that I would really like to be able to do two things with the historical waveforms:
This would allow us to make a capture and keep it in the history - currently old waveforms will be discarded to maintain the configured maximum. Behind the scenes, this could be implemented as a separate queue, or it could be implemented by allowing "pinned" waveforms to bubble to the top and then persist. I'm happy (and able) to configure quite a large history (>100 wfms), so I'm okay with the latter, but others may prefer the former.
In the workflow I've outlined, this would permit a textual name to be associated with the waveform. For example, register values that produced the given waveform. The timestamp is still useful, so I'd suggest presenting this along-side the timestamp.
I've included a nasty mockup below:
The text was updated successfully, but these errors were encountered: