From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-14-2020 09:20 AM
@Intaris wrote:
That chm for me looks empty. I see the index, but it shows nothing where the actual documents should be.....
You have to unblock it first (right click in Explorer).
Downloads are always blocked by Windows, so it won't show the embedded HTML.
12-14-2020 09:21 AM
12-14-2020 09:26 AM
wiebe@CARYA wrote:
@Intaris wrote:
That chm for me looks empty. I see the index, but it shows nothing where the actual documents should be.....
You have to unblock it first (right click in Explorer).
Downloads are always blocked by Windows, so it won't show the embedded HTML.
Well whaddya know. That worked.
It asked me when I opened the chm file, I said OK, but it still didn't show. Once I unblocked it, it works fine. At the risk of outing myself as completely ignorant (once again) - since when does this Properties -> "unblock" stuff exist?
12-14-2020 09:29 AM - edited 12-14-2020 09:29 AM
12-14-2020 09:32 AM
IIRC, This also happens when you download dlls. Nasty, as LabVIEW error messages won't guide you to the problem...
12-14-2020 09:35 AM
How on earth did I use windows in the last X years and NOT come across this even once before?
Sheesh.
Anyway, thanks guys. Learned something today.
12-14-2020 12:46 PM
There were some missing dependencies in the source zip. I also renamed a library to make name collisions less likely.
12-16-2020 10:06 AM
Is anyone else running into bugs? This one is driving me nuts: If the owning VI is a member of a library, and the library is open, then the event handler usually doesn't launch.
12-16-2020 10:40 AM
Here's another one: If the owning VI is set to run when opened, it will start running before the Y Control finishes initializing. (I might have to do some major surgery to resolve this.)
12-17-2020 01:37 PM
Quite a few changes: Cleanup, bug fixes, and kludges to workaround a bug in LV 2018 and earlier (but the installer is smart enough not to include the kludges when installed with LV 2019 +).
If you've made any Y Controls with the prev version, you'll need to remake them.