LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Critical graph scale bug in LV2009?

Put a graph or XY plot in LV2009 on Vista - and set the X scale to be in absolute time. If you do this in LV 8.6 you will now see multiple time stamps along the X axis. In LV2009 you will only get the two at each end.

 

Fill the graph with data...now you may get 1 extra axis point along the X axis...but never more, regardsless of the axis style, - and its position will either be in the middle or at either 25% or 75% of the full time range. (See attached picture of chart and graph).

 

I know this is not how things behaved before,  but is it a bug? Unless I'm overlooking something it is, and it is a show stopper....I hope it's me.

 

If not, a fix should be sent out immediately.

 

plotbug.png

Message 1 of 9
(4,275 Views)

As a work-around*, it is still possilbe to explicitly define the marker values. I hope that helps while we are waiting for a fix.

 

Ben

 

* I admit that this is only a hack to avoid the issue. When the range starts shifting and older data drops off of the chart the code required to maintain a proper set of "X-scale markers" will become cumbersome as well as a CPU hog when the data set reallt get big! 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 2 of 9
(4,267 Views)

Ok, so this is a known bug?

 

I'm depressed...

 

Is there any hope that NI will provide a fix within a short time? This is really ugly.

0 Kudos
Message 3 of 9
(4,262 Views)

Well it is a known bug to those here on the forum.

 

I linked in this thread to the Bug Thread here to make sure this gets added to the list.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 4 of 9
(4,253 Views)

Ok. I tried a few search phrases prior to posting, but could not find anything. Thanks for the help Ben.

 

The marker value trick seems a bit more effective than I first expected..., at least on XY plots with autoscaling on...If you just initialize that property with a set of e.g. 5 evenly spaced X values it will continue to have 5 evenly spaced markers even though the plot is updated with data in an entirely new range....and it will hide markers that you do not have space for if you scale the size of the plot.

 

It's still a kind of bug I would expect NI to turn all attention to and provide a fix for within days or a couple of weeks...It's too big to let slide any longer than that.

Message Edited by Mads on 09-03-2009 08:28 AM
Message 5 of 9
(4,251 Views)

In a project as big as LabVIEW bug fixes that involve changing the actual executable as opposed to changing some VI components, either in vi.lib or in one of the frameworks, is not a matter of days but more like several weeks, especially if it is something like this most likely going very deep into the operational handling of LabVIEW. This bug isn't there because of a typo but most likely because of an addition of some other code that now causes this behaviour. And simply changing it to behave as before might turn other features, specific to 2009 but also earlier ones suddenly into running havoc, so it is definitely not like changing some lines of code and then recompiling the entire thing and voila. It basically has to go through the entire regression test suit on all platforms as well as going through some serious interactive tests of many UI aspects by several guys/gals, before they can even consider wrapping everything up into  a patch distribution. By that time this is done, the impationetly awaited Service pack fix for 2009 most probably is around the corner anyhow, so it will likely get wrapped into that release.

 

Rolf Kalbermatter

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 6 of 9
(4,062 Views)

Sure, it's not an easy task, but that's what you need to do sometimes.

 

If the product had closer competition a wait of 6-12 months for a fix like this would often mean that the customer would head elsewhere...

0 Kudos
Message 7 of 9
(4,058 Views)

There is probably a reason that there seems no serious competition to it, and the patents are certainly not the only reason. Things like the complexity of the task together with the possible market share and revenue are at least as improtant and probably much more important.

 

Remember LabVIEW was in the old days the tool for NI to sell their hardware, where they made a nice profit with, but not to make money with LabVIEW itself. This is probably not as clearly the case anymore but still, I doubt you could make a profit from a LabVIEW like software only. Unless you can sell it as solution to some hardware it is likely to be a failing business.

 

Rolf Kalbermatter

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 8 of 9
(4,048 Views)

Good news - NI has released a fix for this bug (and some others):smileyhappy:

 

Check out the patch here:

 

http://digital.ni.com/public.nsf/allkb/C3F88F3596A164AD86257647006FB022

 

 

0 Kudos
Message 9 of 9
(3,924 Views)