"Notebook" features meta-issue

[602p]

It would be a very handy UX to be able to save a .scopesession file with a number of waveforms and all the context information about how they were captured. 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 means waveforms have to retain the trigger (#361)
• ... and AFG (#418) information they were captured with.
• Will will also want to be able to pin/label history entries (#283)
• ... delete history entries (#343)
• ... and use history entries as sources (#360.)
• Would also be good to be able to add annotations (lines, arrows, callouts, persistent cursors, etc.) to particular waveforms (#424.)

[azonenberg]

For file storage, I think this will require a bunch of settings that are currently global in the scopesession to be moved to the per-waveform metadata (and/or duplicated there, along with "current" settings in the scopesession).

This will also require a lot of instrument properties be snapshotted along with historical waveforms. We'll need to think about how this interoperates with the history window for multi instrument support, especially when dealing with things like a signal generator that don't necessarily create waveforms.

As far as annotations go, this should be a separate ticket as well. Please file one.