String indicator vertical scroll-bar BUG?

[JorgeF]

Hello,

So I ran into this "bug" not long ago.

Normally, when select the scroll bar on any string indicator in labview and drag it up and down, the text moves accordingly.

However, when you use the mouse wheel to scroll and the string indicator is not selected (only the mouse cursor is over the indicator), the text just overlaps endlessly until one moves the mouse cursor over the scroll bar. See the attached image.

This looks like a front panel refresh problem and is not the first one I encounter.

Is anyone else experiencing this issue?

Is it a known bug?

Please let me know!

Thanks

PS: LV 2012 SP1 f4 is what I am using.

[billko]

I tried it and it worked fine for me.  Could you whip up an example really quickly so we can fool around with it and repeat your results?

Off the top of my head, I'm thinking this could be a display driver or (remotely possible) a mouse driver wheel implementation issue.

thanks!

[JorgeF]

Hi Billko,

Thanks to you, I just found out that it is only when the STRING indicator's background is set to TRANSPARENT that it doesnt work. Thats mucho sad 😞

Attached please find the example VI.

[billko]

---

@JorgeF wrote:

Hi Billko,

Thanks to you, I just found out that it is only when the STRING indicator's background is set to TRANSPARENT that it doesnt work. Thats mucho sad 😞

Attached please find the example VI.

---

Wow - VERY reproducable.  🙂

Unfortunately I have no answer.  Sounds buggy to me.

[JorgeF · Accepted solution]

I worked around this issue:

I simply used the same color as the panel's background in the string indicator.

It works.

Thanks Billko

[Todd_Lesher]

It "blurs" for me, too. Unless the indicator has key focus, which highlights it.

[billko]

Furthermore, customizing the control and putting in a background picture doesn't help.  And it seems that the control refreshes itself when the mouse moveseither onto or off of the control.

[JorgeF]

That is exactly what happens 🙂
I'm glad to see I am not the only one with the issue.

Thanks all!

[billko]

---

@JorgeF wrote:

That is exactly what happens 🙂
I'm glad to see I am not the only one with the issue.

Thanks all!

---

I'm kind of sad you aren't.  😉

LOL

[Frozen]

Sad to see that this is still a thing in 2018 😞

Of course the simple work around is to *not* use transparency.