Well, BlessedK, you have once again attached a picture, but no VI, so I cannot determine how you have set the Y Scale Display Format. I'll note in the VI you attached most recently, it was set to 4 digits of precision (which is what your picture shows), despite your statement that you want the Y scale to have zero digits of precision.
My suggestion, once again, is if you want the Y scale to have zero digits of precision, set the Y Scale to have zero digits of precision. If you set it for 4 digits, and want it to have 0, don't complain when it shows you four digits.
The precision for the Cursor, as I've explained, is another matter, one that you can, in principle, manage yourself by creating your own display for Cursor values. One might ask, however, why a cursor should have a precision four orders of magnitude higher than the data being charted, but that an argument about "Do you know what you are doing", as opposed to "Do you know how to do it".
The precision for the Cursor, as I've explained, is another matter, one that you can, in principle, manage yourself by creating your own display for Cursor values. One might ask, however, why a cursor should have a precision four orders of magnitude higher than the data being charted.
I don't know about htis particular case, but LabVIEW has some annoying habits of bunching display resolutions together. So even if the markers on the axis should show no decimal digits for cosmetic reasons, the cursor display still should. You don't want cursor values quantized to the marker resolution.
A probably related, but to me much more annoying thing is that if you export graph data to the clipboard, the output format will use the axis marker format and you could end up with severly truncated data. Se my old comment here. Somebody even made it onto an idea, just kudoed. 😉
I took the VI that I'd downloaded from you (with Y Scale Display Format set to 4 digits of precision), changed it to 0 digits of precision, ran the VI, and got this:
Notice that the Y Scale has ... 0 digits of precision. Here's the VI (as a Snippet):
It should look identical to the one you posted.
It is possible that we are running slightly different versions of LabVIEW, and that you may have found some weird behavior that was fixed in Service Pack 1. I'm running Version 15.0.1f1 (32-bit).
VIs are interchangeable between 32 and 64bit. What matters is what you use to open or build them. (even more importantly, you can typcailly even open them on Mac or linux).
(Of course if you call your own DLLs for example, you need to adjust accurdingly. The conditional disable structure can be used to select between cases where the 32bit and 64bit version must differ.)