Possible Bug with Waveform Graph

[Hatef.fouladi]

Dear Jeff·Þ·Bohrer
could you explain more?! I did not understand whether do you agree with me that such bug exist for invert mood of graph or not ?

[RavensFan]

I've got to ask,  what is invert "mood"?   Do you actually mean "mode"?  Or another word?

[JÞB]

---

@Hatef wrote:

Dear Jeff·Þ·Bohrer
could you explain more?! I did not understand whether do you agree with me that such bug exist for invert mood of graph or not ?

---

On the two graphs this property is different for the X axis scales.  I believe that this explains the X axis range min and max properties you see being reversed as well.  SOME COULD argue that min is min and max is max irrespective of the inverted scale.  I would like some other input from the feature developers before I call it a bug.

[Hatef.fouladi]

Yes my means has "mode"
sorry for my mistyping

English is not my first language

 The bug is that.
suppose I want have a graph that x scale is inverted and start from 5 to 105 and I want to have 5 grid for this scale (every 20 digit one line of grid)
for this reason labview graph has bug and it is impossible to have suck graph in labview

because when you select start in range property node labview get different and false number for  start instead of the digit that you give to start in property node

so if you want see the bug start to make such graph that I mentioned above ( you could not make it due to bug )

[RavensFan]

I did this in LV 2014 and did the following steps.

1.  Drop a new waveform graph.

2.  Type 105 in at the first number on the x -axis

3.  Type 5 in at the last number on the x-axis.

I don't see a problem.

[Hatef.fouladi]

ok  now just create property node and select range for x scale in write mode and try to give some value to increment . you will be see that grid disappear and if you use  property node again but this time in read mode of xscale range you will see that start value is different than what you give it.

   so you could not adjust grid in this mode of graph

see my first commend and try to download vi that I attached  you will see the bug there

[RavensFan]

I added a grab of data before, then a setting of the range, then a grab of the range after.

I'm still not seeing a problem.

[Hatef.fouladi]

indeed you find bug now . just run your code countinusly and try to change Increment and see what happen for grid and start value

[Hatef.fouladi]

RavensFan do you now find the bug ?! or still belive that there is no bug in 

[RavensFan]

Many times, the code works just fine for me.

But there are some times when it loses the grid.  For instance, when I change the increment to 30 or higher.  But when I change it back to 20, the grids come back.

But then after I run the VI multiple times and lose it, I can't get the grid to come back.  (Note that I don't use Run Continuously).

So I agree with you that something strange is going on there.  The one thing I notice is that when the grid goes away, the "Start" part of the cluster becomes some other value that is outside of the range of the Min and Max.  When the grid is able to come back, then the "Start" becomes a value within the range.