W |
Will |
Waveform display screen capture command
Have a command (or better, keyboard shortcut) to snapshot the current waveform display. Currently we have to use WINDOWS screencapture
Activity Newest / Oldest
Tim
(#92915)
"Depending on how capture file sizes are managed, I could see an increased demand for saving screenshots/images vs. full waveform data on the Logic product. Thus, having a ‘Copy Image’ (to clipboard) and/or ‘Save Image’ built-in feature(s) would be more relevant now, especially for efficiently documenting & archiving analog views.
I know Tektronix has this for their PC based software that interfaces to their dedicated desktop oscilloscopes, as does PicoScope (and likely other oscilloscope vendors). Even my old MSO 4034 has a dedicated ‘Save’ button that can create screen image files on local removable storage – just sequentially auto-named as tek#####.png/bmp/tif, each time the button was pressed.
Having a built-in button for this would be a much nicer & more productive method than manually cropping screenshot images each time. User could optionally select the preferred capture view (i.e., waveform image/view only, or everything), but at least having a ‘waveform only’ image capture to file and/or clipboard would be great. You could also do ‘save’ (and auto-name each file like a camera) or ‘save as’ (and prompt w/file save dialog for filename)."
Tim
(#92690)
"I often have to capture oscilloscope measurements as documentation/test evidence. While I can capture a screenshot of Logic, the UI’s layout and especially text size is optimized for viewing on a screen, not as a captured image. It also includes a lot of extraneous (for a static image; not for an interactive UI) elements that add clutter.
It would be very useful to have the option of exporting an image directly (including things like measurements, a legend with the configured channel names, etc)."
Tim
(#87001)
"Would it be possible to add a kind of screenshot feature for Logic 2 window? Maybe just a capture itself and channels name. Thank you."
Tim
discuss.saleae.com/t/quick-poll-problems-you-try-to-solve-with-an-oscilloscope/995/4
"Easy snapshoting, for use in a report. Ideally the snapshot is a simple picture but with relevant metadata, like time of capture o.s.o., can be as simple as adding this info in the file name."
Tim
discuss.saleae.com/t/is-it-possible-to-export-the-screen-as-picture/1159/4
"I use WINDOWS snip and paste into photoshop, and then invert to attain black waveforms on white… much easier to deal with in documentation.
(No need to mimic the old Tektronix and HP displays)
then export to PNG for use in documentation and (lab) notebook notes/PDFs.
With capturing MANY variations/experiments, it would be so much easier and quicker to have a keyboard shortcut to screenshot and go to the next capture."
Tim
Thanks for getting this posted. I hope you don't mind that I changed the title so that I can easily pull this up and search it when needed. I've been meaning to start tracking user interest in this.
We've actually thought about getting native support for an in-app screenshot tool. Long story short, we couldn't justify adding that in, especially when native OS tools can do the same job. Regardless, we've been receiving requests from other users for adding in-app screenshot support, so it's great that you got this posted.
Mark, our CTO and software lead, describes how we worked around this in the forum post below:
discuss.saleae.com/t/is-it-possible-to-export-the-screen-as-picture/1159
Can you let me know any specific limitations you have when using the OS native screenshot tools, and why you'd prefer using an in-app one? Simplicity is certainly what comes to mind for me, but I'm wondering if you had other thoughts.