Since LV 2021 hooking CfgGetDefault is not enough. There are two new classes in the mgcore library: LazyConfigValue_Bool32 and LazyConfigValue_PathRef. I assume, they're introduced for faster access to the token values. I always used good ol' WinAPIOverride by Jacquelin Potier to catch API calls (including LV ones), but now it seems that it lacks some necessary functionality (e.g., custom actions on a BP hit). So I decided to adapt that Lua script.
Not that I'm a big fan of scripting languages, plus Lua in CE acts odd sometimes, so this script is far away from ideal. It also hooks only a few LazyConfigValue functions as the rest doesn't really matter. Now here's what I've got.
Launching LabVIEW:
Creating a new VI:
Doing various stuff in there (incl. building an EXE as the last operation):
No new tokens on the VI close or LabVIEW exit. Did I grab them all? Very unlikely. But I think, tokens for most common scenarios are on the list. And there are some interesting ones.
I thinks you are right, you grab them all.
But by time there will be new tokens when there will be any updates in version.
I found some more hidden INI keys
in LabVIEW General
Posted
I thinks you are right, you grab them all.
But by time there will be new tokens when there will be any updates in version.