05-27-2020 10:28 AM
Update
When I compiled the application, the hover worked at least for the few times I tested.
I can put non customized booleans that have the hover effect in LabVIEW 2019 64bit, and they work. However, as soon as I customize them, the hover effect no longer works. Extremely frustrating.
mcduff
05-29-2020 02:15 AM
@mcduff wrote:
Update
When I compiled the application, the hover worked at least for the few times I tested.
I've seen it go wrong in executables as well. But it's more rare.
@mcduff wrote:
I can put non customized booleans that have the hover effect in LabVIEW 2019 64bit, and they work. However, as soon as I customize them, the hover effect no longer works. Extremely frustrating.
It's not a global effect. I've seen the bug in one clone of a VI, where other clones still worked.
I haven't tested non customized Booleans, so it could be that they are not effected all. Or they simply didn't get triggered to get the bug.
05-29-2020 12:33 PM
What was weird for me was I had a Front panel of customized buttons where the hover did not work. I dropped a System or NXG style button on that same panel; the hover for those worked while the others did not.
I haven't tried LabVIEW 2020 yet, but a little bird told me the CAR was closed. Not sure what that means, whether it is fixed or just forgotten about. The CAR does not appear on the 2020 upgrade/README notes.
mcduff
05-29-2020 01:09 PM
@mcduff wrote:
I haven't tried LabVIEW 2020 yet, but a little bird told me the CAR was closed. Not sure what that means, whether it is fixed or just forgotten about. The CAR does not appear on the 2020 upgrade/README notes.
Is this it?..
Bug number: 166386
Description:
Incorrect behavior when using a Boolean control from the System paletteWhen using a Boolean control from the System palette and running the VI, you do not see the "hover" picture change. When clicked, the value stays consistent, but the button does not change visually.
Workaround:
Do not use the System Boolean buttons or place them inside another structure.
Details:
Reported Version: LabVIEW 2017 SP1
Resolved Version: LabVIEW 2020
Added: Apr 20, 2020
I did a quick test in LabVIEW 2020 in both IDE and EXE and didn't see the bug yet. Hope it's fixed now.
BTW, it turns out, CAR number does not equal to Bug number. It was assigned CAR # 718053, but Bug # is 166386. 🙄
05-29-2020 03:18 PM
@dadreamer wrote:
@mcduff wrote:
I haven't tried LabVIEW 2020 yet, but a little bird told me the CAR was closed. Not sure what that means, whether it is fixed or just forgotten about. The CAR does not appear on the 2020 upgrade/README notes.
Is this it?..
Bug number: 166386
Description:
Incorrect behavior when using a Boolean control from the System paletteWhen using a Boolean control from the System palette and running the VI, you do not see the "hover" picture change. When clicked, the value stays consistent, but the button does not change visually.
Workaround:
Do not use the System Boolean buttons or place them inside another structure.
Details:
Reported Version: LabVIEW 2017 SP1
Resolved Version: LabVIEW 2020
Added: Apr 20, 2020
I did a quick test in LabVIEW 2020 in both IDE and EXE and didn't see the bug yet. Hope it's fixed now.
BTW, it turns out, CAR number does not equal to Bug number. It was assigned CAR # 718053, but Bug # is 166386. 🙄
Good Catch!
mcduff
PS How do find all of those hidden ini settings? 😉
05-30-2020 02:20 AM
@mcduff wrote:
PS How do find all of those hidden ini settings? 😉
If you mean that thread on LAVA, then I used the same basic principle proposed by flarn on the first page of the thread. I just used another software for it. I think, it's a quite an off-topic here, so it might be better asked somewhere else. 🙂