Re: Graph Xscale properties don't work well with multipliers
The deal is that the image you see is not the image stored in memory. For sample sets with points larger than the pixels on your screen, LabVIEW will truncate/interpolate/labview magic the dataset to create an representation of your data for display. Setting your mouse to a specific data location will often result in a little movement to get to the closest point that is displayed. Workarounds include using a HUGE monitor or displaying fewer points at a time.
Re: Graph Xscale properties don't work well with multipliers
Excellent explaination for what is actually happening here. The workaround that I used was to take the specified cursor location, use the waveform graph X scale range property node of MIN and MAX at +/- 1% of the cursor location prior to specifying the move and then returning the graph back to the original Xmin and Xmax after the move.
Graph Xscale properties don't work well with multipliers
I have a wave form graph. High sample rate data (5Khz) is displayed on the graph and the x scale has the appropriate multiplier to show in seconds. I use the property node to move the cursor and another property node to read the cursor position. The specification for the move does not agree with the indicated position. Increasing the value for significant digits or digits of precision in the wavefrom properties does not improve the situation. If I change the x range to zoom in around the intended cursor position and then perform the cursor move, I get agreement between specified and indicated cursor position. I can zoom out and still get agreement. Therefore,the only way to get agreement is to first zoom the graph in on the intended value and then perform the cursor move before showing the normal graph. Seems like there is a bug in waveform module... Has anyone encountered this?
