I am progressively removing pieces of code in my programs, formerly dedicated to exporting ASCII files of graph data, thanks to the (relatively) new "Export Data to Clipboard" contextual menu item.
However, recently, I have been bitten by a subtlety that is not documented (or not readily accessible): the exported values strictly stick to the data display format of the object (be it a graph, an array or whatever else).
Let's take an example:
XY graphs allow you to specify the precision used for scales, using a nifty contextual menu item on the scale legend. The problem is, the choice is limited to 6 digits. Now before you start laughing at me and demonstrate how ridiculous it is to want more than 6 digits of precision, let's examine this real life example: I am computing an autocorrelation curve from 0 to 1 ms in 1 us steps. In this case, I do need to choose a display precision of 6 for the axis, otherwise the exported data will be truncated to the specified precision. Of course the resulting data will be useless for whatever post-processing I want to do with another software. Luckily, I haven't needed to do the computation with 0.1 us resolution, because I would then be out of luck.
A side effect of this is that you have to specify a ridiculously high precision for export purpose, when for display purpose, you would be happy with much less, as shown below:
<------------ I don't need 6 digits of precision for display!
So, in summary, at least for graphs, you can't specify arbitrary precision (suggestion 1: fix that) and you need to specify the scale precision for export purpose even though it might result in an ugly aspect (suggestion 2: disconnect the two settings).
The problem is compounded for other objects (scalar, arrays, etc) where you CANNOT specifiy the display precision at run time! If you miscalculated the precision needed to display a value, or chose the wrong display format and try to copy the data (or export it in the case of an array), you'll end up with truncated data. So here, same suggestions:
suggestion 1 bis: allow the user to change the display format of any numeric at runtime without limitations
suggestion 2 bis: differentiate between export/copy precision/format and display precision/format. I would suggest specifying this as a generic property for a given VI's FP objects, as well as individually via a Property Node. Again, I am not talking about display format, but EXPORT format.