03-28-2012 02:46 PM
Too bad the number displayed in the Std I/O Window wasn't 42, becuause then we would know the answer 🙂
Ben- the Std I/O Window shows a LabVIEW icon in the upper left corner. Is that because LabVIEW is calling the dll (which may be outputting to I/O), thus Windows thinks the owner of the window is LabVIEW?
Just curious.
-AK2DM
03-29-2012 02:30 AM
@AnalogKid2DigitalMan wrote:
Too bad the number displayed in the Std I/O Window wasn't 42, becuause then we would know the answer 🙂
Ben- the Std I/O Window shows a LabVIEW icon in the upper left corner. Is that because LabVIEW is calling the dll (which may be outputting to I/O), thus Windows thinks the owner of the window is LabVIEW?
Just curious.
-AK2DM
Yes that is the reason. And the window looks suspiciously like a LabWindows CVI edit window with the status bar underneath and the selection mode icon.
03-29-2012 02:37 AM
Since the DLL was written in LabWindows/CVI, this doesn't come as so much of a surprise^^
Oh well, I'll just drag it somewhere, it does not bother me. As long as it doesn't popup in the built executable later, everything will be just fine.
03-29-2012 03:07 AM
Well, unless your buddy disables that debug window in the release build of his DLL, this window WILL popup in a LabVIEW executable too!
03-29-2012 07:31 AM
@rolfk wrote:
...Yes that is the reason. And the window looks suspiciously like a LabWindows CVI edit window with the status bar underneath and the selection mode icon.
Kudos all around for...
Asking a good question,
Pointing out what I missed,
providing yet another bit of knowlege to my overloaded grey matter.
Thank you!
Ben