Rif.: LabVIEW front panel gets corrupted : bottom half doesn't update/scroll anymore.

[ThomasV]

Hi,

I'm a seasoned LabVIEW developer (+20yrs), and I've had this issue in multiple projects,

since LabVIEW 2011. Now in my LabVIEW 2019 projects I am still experiencing it sometimes :

I have GUI VI, that all of a sudden get corrupted. I stops to update the bottom part of the window,
during runtime but also in edit-mode.
So the effect is that the bottom part of your window is frozen, but the upper part is still alive.

E.g. if you are in edit-mode, and you scroll with the mousewheel up and down, the front panel scrolls, but the bottom parts remains frozen.

The issue sometimes occurs immediatly when the VI is opened, but sometimes it takes a minute or so before it occurs.However when it occurs, it doesn't go away anymore untill you close the VI.

I've opened a discussion in the past, and thought I got a solution, but in the end the solution didn't work.

See : https://forums.ni.com/t5/LabVIEW/LabVIEW-Front-panel-bottom-part-not-updating-at-runtime/m-p/3811200...

Up till now my only solution was to recreate the entire VI by copying the entire block diagram to a new VI and then cleaning up the
front panel.

However in my current project, I have the issue again, and I cannot recreate the VI, because my multilingual toolkit uses the UID's
of all front panel objects. These UID's will change when copying to a new VI, so our language database will be useless.

I have attached 2 such corrupted VI's. (I've disabled the code and disconnected type definitions so you can open it without issues)

Please just scroll up and down with the mouse wheel. Th issue should occur in a minute or so.

I hope someone finds a way to repair these VI's.

Thx, Thomas.

[pincpanter]

Your vi contains IMAQ image indicators. I don't have IMAQ, so the vi is broken. Furthermore, if I click on any IMAQ indicator or even its terminal, LabVIEW hangs and runs crazy with high CPU usage.

[ThomasV]

Could you try the other vi that I uploaded? No imaq there.

Also don't run the VI. Remain in edit mode.

[JensG69]

I scrolled like crazy for several minutes in your VI_2, no problem at all.

Regard, Jens

[RavensFan]

I also didn't have any problems with either VI when I scrolled for a few minutes while it was in edit mode.

[pincpanter]

---

@JensG69  ha scritto:

I scrolled like crazy for several minutes in your VI_2, no problem at all.

Regard, Jens

---

Me too. Actually I easily saw the problem with User Interface.vi, with or without the IMAQ controls.

[pincpanter]

---

@ThomasV  ha scritto:

However in my current project, I have the issue again, and I cannot recreate the VI, because my multilingual toolkit uses the UID's
of all front panel objects. These UID's will change when copying to a new VI, so our language database will be useless.

---

Do you have many free labels around? I use string indicators to manage multilanguage, so I don't need fixed UID's.

[ThomasV]

Strange, i have the issue with both vi's on multiple pc's.

The uid-option also allows me to translate static texts on the front panel.

Thx!

[JensG69]

OK, I have to revise my first statement, I get the effect on both of your VIs, very quickly when I move the frontpanel from my laptop monitor to an external one.

The effect is fixed after maximizing the frontpanel.

Seems also to happen not (or less often), if the frontpanel is maximized.

Really strange.

Regards, Jens

[altenbach]

I see the same problem. It gets fixed once you set the minimum panel size back to 0,0 in the windows size property page. I think it has to do with this setting.

(There might be a corruption. If I set it back to your size later, the problem disappears)

I would also get rid of all these overlapping objects. I am sure there is a better way to organize the panel.