LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Tom_O

Right-click -> Copy Data should copy TEXT data

Status: New

When debugging (and at many other times), I want to copy data from a probe or control into a text file, Excel, whatever.

 

For reasons that I am totally unable to fathom, it copies the control as a bitmap. Print screen provides this functionality already. I think copy data should copy text instead!

 

copy_data.png

 

I wasn't able to find this on the exchange, sorry if I missed it!

10 Comments
Intaris
Proven Zealot

Or simply build in the same export functions which are available for graphs.  Then the exporting is the same as on other controls already present.

joaopam
Active Participant

Life is full of coincidences, I need this function too.

Intaris idea is good also, use the same export functions which are available for graphs...

Kudos...

Mondoni
JÞB
Knight of NI

Export to excel or export to text I could agree with.  "Copy Data" currently does the exact same thing as "Copy Data" does on any other control or indicator in LabVIEW.  lets not change how that method works just because a control is in the Probe Watch Window.  How would this effect those of us that have custom probes that we also use in our vi's? ~~~~~Shudder~~~~~


"Should be" isn't "Is" -Jay
Tom_O
Member

I propose this happens for all controls and probes, anywhere where you can see "copy data". Custom probes wouldn't need to change, as there would be a copy method associated with the datatype already. An additional custom method could be an option.

 

Intaris' added export option would be a great alternative.

TrevMrgn
Member
I agree. 'Copy Data' should copy the data. It shouldn't copy an image of the control the data is in. Perhaps the 'Copy Data' menu entry should be changed to 'Control image' or something.
JÞB
Knight of NI

I think you a just a bit confussed when you say "Custom probes wouldn't need to change, as there would be a copy method associated with the datatype already."

 

Probes ARE controls.  Controls have a "Copy Data" method.  Your proposal would change that methods behavior.  I don't find that idea very appealing.  Adding a "Export data to clipboard" method would be better than changing the behavior of an existing method I use frequently.


"Should be" isn't "Is" -Jay
Tom_O
Member

Fair enough, I didn't really see a use for copy data in its current form, but if others use it then best to add the export option.

 

Re custom probes, I just meant you wouldn't need to write the copy data method for your probe as it would inherit from the control.

Broken_Arrow
Active Participant

Kudos to variant "Export data to clipboard" as suggested.

Richard






shb
Active Participant
Active Participant

It is possible to export to clipboard in several formats at the same time. The destination application picks the best matching format. Some even allow to select which format to use (example: office applications)

So why not export in multiple formats? (Maybe only on windows.)

Christina_R
Active Participant

I agree we need better importing/exporting through the system clipboard, but I want to explain that the menu item is "Copy Data" and not "Copy Image" because within LabVIEW, the data can be copy/pasted between controls of same datatype.


Christina Rogers
Principal Product Owner, LabVIEW R&D