05-18-2017 07:20 AM - edited 05-18-2017 07:26 AM
@JÞB wrote:
Exactly.
The context in which the process runs and NOT the OS bitness.
Err?? Yes I use the context in which the process runs but only if the executable is a 32 bit program. Otherwise it is clearly a 64 Bit OS. If the 32 bit process runs in the SysWOW64 context, then it must be a 64 bit system too. Only if SysWOW64 returns FALSE, is it a 32 bit OS.
I do use the context but conditionally!!
Basically:
if (process == 64Bit)
return 64_bit_OS;
else if (SYSWow64 == TRUE)
return 64_bit_OS;
return 32_bit_OS;
05-18-2017 07:35 AM
Facepalm
05-18-2017 07:57 AM
@JÞB wrote:
Facepalm
If it makes you feel any better, I was very much tempted to "fix" the VI after having it downloaded and looking at it. Only after thinking it completely through and running it to verify the fix and finding that it worked wrong, did I realize that it had been correct before!
05-18-2017 08:06 AM
@rolfk wrote:
@JÞB wrote:
Facepalm
If it makes you feel any better, I was very much tempted to "fix" the VI after having it downloaded and looking at it. Only after thinking it completely through and running it to verify the fix and finding that it worked wrong, did I realize that it had been correct before!
Yes, I got caught with the similities to the gem and totally missed the minor but somewhat pointed difference
05-19-2017 01:15 PM
On to the next nugget, please!
How's this?:
Control-double-click a VI's icon to open its block diagram.
This can be useful for closing hung VIs during development:
If you have a VI that is hung but has not crashed LabVIEW, and the VIs stop button is not shown, you can quit the VI by opening a new VI, putting the hung VI on the block diagram, and control-double-clicking the icon to open the hung VI's block diagram. Press stop.
05-19-2017 01:49 PM
@littlesphaeroid wrote:
On to the next nugget, please!
How's this?:
Control-double-click a VI's icon to open its block diagram.
This can be useful for closing hung VIs during development:
If you have a VI that is hung but has not crashed LabVIEW, and the VIs stop button is not shown, you can quit the VI by opening a new VI, putting the hung VI on the block diagram, and control-double-clicking the icon to open the hung VI's block diagram. Press stop.
Here is a "force multiplier" for the micro-nugget.
That will also work from the VI Hierarchy screen and if you hit "ctrl-a" it will also show re-entrant VIs that where launched dynamically and running top-level. So your trick will let you open the diagram of the one instance you want to investigate.
Ben
05-19-2017 02:27 PM
You can use the CTRL+Double click on running VIs as well, but you need to turn auto tool off since CTRL functions differently when it is on, switching to the breakpoint tool. As for aborting running VIs I use my LabVIEW Tray Launcher which (among other things) has a way to abort all VIs, in all versions of LabVIEW, except for asynchronous clones at the moment.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
05-22-2017 02:17 AM
I use this vi that I found a while ago. Simply run this (double-click it) whenever needed.
I take no credit for it whatsoever. If it is yours, I salute you and would like to say a big thank you for it. It has got me out trouble quite a few times during development. I hope you don't mind me sharing it here.
05-22-2017 10:25 AM
@sebster wrote:
I use this vi that I found a while ago. Simply run this (double-click it) whenever needed.
I take no credit for it whatsoever. If it is yours, I salute you and would like to say a big thank you for it. It has got me out trouble quite a few times during development. I hope you don't mind me sharing it here.
CAUTION: the attachment above is saved with "Run When Opened"=True!
05-22-2017 10:33 AM
Apologies!! I forgot I had it set that way when I saved it on my system for ease of use.
I've re-saved it with this option set to False.