05-15-2017 03:50 PM
@BowenM wrote:
I found the need to find if an application was running on 32 or 64-bit Windows. Forum searches only brought me to a LAVA page and a rolfk attachment that returned
"The page you are trying to access is not available for your account."
Strange! When I click on the attachment in the LAVA post I get the VI downloaded.
05-16-2017 12:13 AM
@GregSands wrote:
Haven't seen this micro-nugget before - if you hold the Delete key down, then objects are immediately deleted as you click on them. Not hugely useful, but who knew it? Works on the BD and FP since at least LV2012 (earliest I can check at the moment).
I have never really know this till now. Additionally by clicking and selecting multiple items deletes them all!. Thanks for the nugget.
05-17-2017 12:25 PM
@rolfk wrote:
Strange! When I click on the attachment in the LAVA post I get the VI downloaded.
Log out of LAVA and try it again. I don't have an account at all.
05-17-2017 02:04 PM - edited 05-17-2017 02:05 PM
@BowenM wrote:
Log out of LAVA and try it again. I don't have an account at all.
You can log out of LAVA? LAVA like many forums require you to login to download off of the site. The error message "For your account" I likely because if you aren't logged in you are on a Guest account.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
05-17-2017 02:19 PM - edited 05-17-2017 02:25 PM
@Hooovahh wrote:
@BowenM wrote:
Log out of LAVA and try it again. I don't have an account at all.
You can log out of LAVA? LAVA like many forums require you to login to download off of the site. The error message "For your account" I likely because if you aren't logged in you are on a Guest account.
Sorry Hooovahh, Rolf
I get this from here
https://lavag.org/applications/core/interface/file/attachment.php?id=4191
until I actually log in to get this download
which isn't much different than the Hidden Gem
which also depends on the LabVIEW Context as explained here
05-18-2017 01:49 AM - edited 05-18-2017 01:52 AM
05-18-2017 05:43 AM
@JÞB wrote:
which isn't much different than the Hidden Gem
I never said it was, and as far as chronology goes, the LAVA post predates the Gem quite a bit.
which also depends on the LabVIEW Context
What do you mean by this? This conditional compile setting is not depending on the VI being part of a project like a few others. It will be always set to the value for which the VI is currently compiled, which is also deterministic outside of a project.
05-18-2017 06:38 AM - edited 05-18-2017 07:07 AM
@rolfk wrote:
@JÞB wrote:
which isn't much different than the Hidden GemI never said it was, and as far as chronology goes, the LAVA post predates the Gem quite a bit.
which also depends on the LabVIEW Context
What do you mean by this? This conditional compile setting is not depending on the VI being part of a project like a few others. It will be always set to the value for which the VI is currently compiled, which is also deterministic outside of a project.
We should probably branch this but... Assume that a developer had a 64 bit processor and a 64 bit OS and LabVIEW 201x x32 and x64 installed side by side.
(I don't have a system like that too test)
From my understanding after reading the help.
The vis attached to my reply will return the bitness of the LabVIEW IDE and not the bitness of the OS or CPU.
The desired return is the OS bitness. WHICH is supposed to be agnostic of the hardware or the context of the program it enables to run
05-18-2017 07:00 AM
@JÞB wrote:
From my understanding after reading the help.
The vis attached to my reply will return the bitness of the LabVIEW IDE and not the bitness of the OS or CPU.
The desired return is the OS bitness
The logic, in my VI at least, is as follows:
If the current executable is 64 bit, the OS MUST be 64 bit (you can't run a 64 exe on a 32 bit system).
Otherwise determine if the current process is running as WOW64 process, if so it is a 32 bit process running in the 32 bit compatibility layer of 64 bit Windows. Otherwise it must be a 32 bit OS.
05-18-2017 07:13 AM
Exactly.
The context in which the process runs and NOT the OS bitness.
(Don't Make me go full circle and suggest a hack like looking to see if a folder exists)