Problems showing traces on a strip chart with cvi 8.1.1

[John_Sch.]

I have code that charts temperatures inside a temperature chamber.  This code is shared between several applications.  It has worked for months.  It seems to now have a problem with a new application.  The strip scrolls to the left and time labels are shown and update correctly on the x axis.  Evently the trace are not being updated even though the strip chart is still scrolling and getting correct time stamps.  Eventually the exisiting trace scroll off the screen and no data can be seen.  If the user resizes the panel and waits for the next update ( 10 second period) the strip chart will refresh and show all the missing data but will not show then future data when it should.  I do check the results value returned from every command and do not get an error.  See attached screen shot.

[CreviceDweller]

I had this problem too.  It occurs in 8.1.1 when any control overlaps any part of the stripchart.  Even if the control is not visible.  Resize and rearrange your controls so they can't overlap the stripchart and it should work as it did before. 

[LuisG]

CreviceDweller,

I believe the bug you're referring to only happened in CVI 8.5. Are you sure you saw this same behavior in CVI 8.1.1?

Luis

[John_Sch.]

Yes it is version 8.1.1

I saw the other thread that relates to this.  I am not sure that I have the same problem.  I do have controls on top of the strip chart.  I will move them to see what happens.  I just have not yet done that.

[John_Sch.]

I moved the other controls to NOT be on top of the strip chart and that fixed the problem !

This does not explain why one of my applications had this problem while another did not.  (They shared the uir file)

But this fixes the problem and I am moving on.

Thanks

[LuisG]

Thanks for the update, John.

It's definitely unexpected that you ran into this bug in CVI 8.1.1. My guess is that even though you're using the CVI 8.1.1 ADE, you might have the CVI 8.5 runtime engine installed (c:\windows\system32\cvirte.dll) and that would explain it. Or maybe it really is a different issue than the one I was thinking of.

But since you've already worked around that problem, then I guess the situation is resolved.

Luis

[John_Sch.]

Since you mentioned it,  I looked.

You are exactly correct on the version numbers.