LabVIEW front panel "tearing" display glitch

[glitched]

I'm getting this bizarre display glitch in LabVIEW 8.0 (and 8.0.1) where the right 1/5 to 1/3 of the front panel suddenly "tears" itself, rendering that section unusable. This either happens while the VI is running and I click certain buttons or navigate using the horizontal scrollbar, or when I bring the VI in edit mode to the foreground (see attached screenshots). I tried setting various VI properties like scaling objects on the front panel, maintaining the display proportion, eliminating the horizontal and vertical scrollbars, etc., but that hasn't worked. The only way to fix it so far is to minimize or restore down the front panel and then re-maximize it, which is a pain to do each time the glitch appears. Has anyone else encountered this problem, or have any ideas on how to fix it? Thanks!

[AnalogKid2DigitalMan]

This does sound familiar:

http://forums.ni.com/ni/board/message?board.id=170&message.id=176426&query.id=43763#M176426

Unfortunately, the poster never followed up with NI to help diagnose the root cause. You may want to spur them into looking at replicating the behavior if you post your vi.

Are your video drivers updated?

[glitched]

Thanks for the quick reply! Yes, I saw that thread too, but I wasn't able to save for a previous version (it gives me a bunch of errors like BuildHelpPath.vi, Cannot save VI from VI.LIB to previous version). I just updated my video drivers, but it didn't help. I also have the same difficulty as the other user (FLT CTRL 6) due to the proprietary nature of my VI. Unfortunately, I think the glitch might have something to do with the number of front panel and/or block diagram controls/indicators/graphs I have, so it'd be hard to reproduce in some demo VI. I heard that LabVIEW 6.0 had this 555 limit on front panel objects, but supposedly that was eliminated in future versions. In any case, I doubt my front panel objects even comes close to that limit, although I do have a large number of graphs up.

[glitched]

Alright, I stripped down my glitched VI and attached it, so please try it out. It looks like the number of front panel objects isn't the issue, as the glitch is still there with just two graphs in a tabbed container.

For me, the front panel tearing either appears right after I run the VI, or if I run and then scroll left/right and up/down with the scrollbars. Let me know if you guys don't encounter the glitch on your systems, in which case it might be a hardware display issue on my side. Thanks!

[Joe_H]

It is definetly something wrong with this vi. it is doing all kinds of weird things on my PC also.

Check it out

Message Edited by Jhoskins on 08-11-2006 06:45 PM

Message Edited by Jhoskins on 08-11-2006 06:49 PM

[gmart]

It looks like the block diagram window somehow is offscreen to the far left. If you right-click on the window item on the Windows Start area and select Move, you can eventually move the window back into the visible desktop area (by pressing the right arrow many times). The front panel drew funny until I did that.

[JeffBoettcher]

Thank you for including a VI that shows this behavior.  I have filed a bug report including your VI, ID# 40D79E1W.  For the time being, you may find that copying the contents of your VI's diagram into a new VI will resolve the problem.

[RRRRSSSS]

Has a solution to this problem been found??

I'm currently having the same problem.

LV 8.01

My Vi has a tab control as in the other problem vi's.

I have also been using 2 monitors if this helps trouble shooting the problem.

[Doug M]

As Jeff mentioned this issue has been reported to R&D and is being investigated.

[JeffBoettcher]

Hello RRRRSSSS,

If you have a VI that displays this behavior reproducibly, particularly if you can strip it down to only UI components (no subVIs, for simplicity of posting) and could attach such a VI to this thread, along with steps we can take to reproduce the behavior with your VI, that could help our developers investigating the issue.

I understand it may not be easy to simplify things to that degree or you may not be allowed to post your code, in which case we'll continue investigating with what we have.

Thanks for your help and patience.