UI Graph showing horizontal lines for each data point no instead of plotting across the screen.

[AllenInIowa]

I have a graph which shows a plot of frequencies and power values from two arrays of floating points.  It has worked fine until recently, and now it just shows horizontal lines across the entire graph for each data point:

The code hasn't changed, but I did move this Panel from one .uir file in to a new .uir file via panel copy/paste.  I also found a situation where menubar items with no sub-menus started showing exclamation marks and I had to add an ATTR command to disable that.  It seems there may have been some settings in the original UIR file that did not survive a copy/paste.

The graph one is problematic, since I can go back to a version of the original .uir and compare all the exposed settings and they match the current.

Is anyone familiar with what could cause the graph to think it just has one entry column instead of a bunch of columns to plot?

Thanks for any tips on what attributes or functions I should read up on in the docs.

[AllenInIowa]

Odd. I just made a test program using a graph, and by default it works as expected. I can't even figure out how to make it do the horizontal line thing.

Have I stumbled in to a bug or some corruption of the .uir file, maybe?

[AllenInIowa]

I made a new GRAPH inside my big program, and it worked -- but as soon as I enabled Cursors, it starts doing the horizontal line thing. Odd, that.

[AllenInIowa]

Okay, this must just be some form of corruption in the UIR file. My new control now stays messed up even when I remove Cursors.  My standalone test program does not mess up.  Unless someone finds this post and knows what causes this, I'll just assume it's a "strange LabWindows thing" and see if I can recreate the UI graph from scratch and hope it doesn't mess up again.

[AllenInIowa · Accepted solution]

UPDATE:

The data we use used to be floats, but was changed to doubles for reasions.

The PlotXY still had VAL_FLOAT so it was mis-using the data in the array that was passed in (an array of doubles).

Changing it to VAL_DOUBLE resolved this issue. Whew.