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.
The VI doesn't store patch -- patch doesn't change the version number of LabVIEW and does not change the information of a VI. That's why any patch can't modify the load/save formatting.
Service Pack you already have -- that's in the version number.
Bitness is something that some but not all VIs store. A source-only VI doesn't store bitness. But for those that do have a compiled code segment, we could dig up that information.
Nice remark, fabric, but sadly doesn't help. It states the bitness of the OS, not of the LV editor you are using.....
In your example, both LV 32bit and 64bit would run with "True" when running on a 64bit OS (which is naturally required for LV 64bit, but not for the 32bit!).
Norbert
Norbert ---------------------------------------------------------------------------------------------------- CEO: What exactly is stopping us from doing this? Expert: Geometry Marketing Manager: Just ignore it.
Norbert: On my machine that code snippet returns the *editor* bitness correctly. It returns false when run from the LV2012 32-bit IDE on a 64-bit machine.
Ah, ok, i see what i did wrong: I failed to create the TARGET_TYPE==32 case. I somehow assumed that, in case that the case '==64' isn't true, the disable would remove the TRUE constant hence leaving "an emtpy tunnel" which should result in a FALSE. Obviously, the Conditional Disable structure doesn't work like that.
Lesson learned:
Never place a Conditional Disable structure with only a single case. Implement the alternative as well (aka. DEFAULT).
Norbert
Norbert ---------------------------------------------------------------------------------------------------- CEO: What exactly is stopping us from doing this? Expert: Geometry Marketing Manager: Just ignore it.
> The idea is not about the VI it is about the editor!
The picture you posted is about getting information from a VI on disk about which version it was last saved with. That's why it takes a VI path as an input. I assumed that meant you wanted the bitness, etc., that the VI was last saved with. If you want the properties of the editor in general, they do not belong on that method.
If you're using that method currently to get the version of the editor, you should stop. That will give you the version number of the editor used to edit that VI, NOT the version of the editor you are currently running (unless you're creating a VI, saving it, and then calling that method).