Chart Display in Subpanel not as expected

[klessm1]

I am running into kind of a unique problem with viewing a chart inside a subpanel.  I am running into this issue in 8.5.1, but have also seen it in 2009.

I am creating multiple copies of a reentrant vi using vi server and then displaying one instance at a time in a subpanel and use a slide selector to change which instance I am viewing.  In the reentrant vi I have a chart in strip chart update mode that displays data on a time scale.  For some reason if I switch between the instances the data in the chart disappears, but the new data shows up correctly on the x-axis.  I also found that all of the "lost" data reappears if the scales are modified.

I am guessing that it has something to do with LabVIEW not having to refresh the entire chart when the front panel is not being shown.  I would have thought that it would remember what was drawn though.

Note that the chart displays fine when in the other two update modes, however they are not appropriate for my application.

Does anyone know of a quick fix to force the chart to update the entire display when in the strip chart update mode?

Thanks.

[klessm1]

I was able to get around the issue by trying to force the chart to update the display.  I did this by:

1. deferring front panel updates

2. changing the Y scale

3. changing the Y scale back

4. enabling front panel updates

It works but is not very pretty.  Would like to see if there is an easier way to force the updates (didn't see a method or property for this).  Or if this is really a bug that should be fixed.

Thanks

[Pnt]

An example vi whould help

[Ben]

---

klessm1 wrote:

I was able to get around the issue by trying to force the chart to update the display.  I did this by:

1. deferring front panel updates

2. changing the Y scale

3. changing the Y scale back

4. enabling front panel updates

It works but is not very pretty.  Would like to see if there is an easier way to force the updates (didn't see a method or property for this).  Or if this is really a bug that should be fixed.

Thanks

---

To prevent an issue in the future with your ears burning when the person who follows in your footsteps looks at that code, please include a commnet in your code explaing why you did like that.

Yes post an example taht demo's the problem so we can it logged and fixed.

Ben

[klessm1]

Haven't been able to put together a good demo showing the issue.  I may have to take the original and start stripping stuff out of it.  When starting from scratch I wasn't able to reproduce the failure.  Don't you just love those issues!

Right now I am on a very tight schedule so I don't have too much time to invest in it, but I will eventually send some code out.