05-21-2021 11:30 AM
@altenbach wrote:
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.
I can confirm this!
05-21-2021 11:48 AM - edited 05-21-2021 11:58 AM
Only one of the VI's (the less urgent one 🙄) has the minimal window size set to something else but 0,0.
So this is not the root cause 😢
Setting to (0,0) doesn't fix it for me.
05-21-2021 12:15 PM
A temporary fix that works (during runtime)
Move the window bounds programmatically 1 pixel every second (and back).
I can force the issue to apear mostly by putting another application frontmost and then switching back to labview.
when scrolling the issue apears, and gets fixed when the window moves a pixel.
However this is a VERY temporary fix.
05-21-2021 12:36 PM
Hi Thomas,
played around a lot with your Interface_2. I see the flaw in edit mode, usually very fast when pulling from one screen to another or after resizing the frontpanel manually. Maximizing the window fixes it. But you are correct, it will appear again. I even tried to save in LabVIEW 2020, then convert back to 2019, giving your tab control a color other then transparent, removing some of the decorations. No effect.
Sorry, I have no solution for you other than recreating the VI (I know you said that's not a solution... - and you already know about that).
It's a known fact that sometimes something in a frontpanel might get corrupt (after many saves and/or after several LabVIEW version upgrades).
Regards, Jens
05-21-2021 12:54 PM
Yes, Sorry I only looked at one of your VIs (on a laptop currently). I still think the main problem is the immense number of overlapping objects. I'll have a look at it on a better computer later.
05-24-2021 01:44 AM
@ThomasV ha scritto:
The uid-option also allows me to translate static texts on the front panel.
Thx!
Obviously, finding and correcting the problem would be the best. Maybe altenbach is right pointing against the high degree of overlapping.
What I meant is that I do the same thing: translating text. However, rather than use "static text" (i.e. free labels), I place transparent string indicators (disabled) whenever a caption is not available. I think it's a viable alternative, unless you have tons of strings around.