11-15-2006 10:18 AM
11-16-2006 06:58 PM
11-17-2006 12:32 PM
11-20-2006 10:46 PM
11-27-2006 10:19 AM
I'm attaching a zip file to this post. It contains 8 files:
My Desktop properties are as follows:
I'm still puzzled as to why my laptop showed the border in the built application up until I changed my color quality to 16 bit, and now that its back to 32 bit there is no border.
Thanks for any feedback you have.
Steve
11-28-2006
06:22 PM
- last edited on
06-19-2025
09:01 AM
by
Content Cleaner
Steve,
When taking a look at your files, I can see that the border does not show up when running the executable but it does show up when running the VI. However, as I mentioned previously, there is no combination of settings that I can find to show the border when the code runs as an executable. Even when creating a new VI into an executable, this does not appear correctly on any of the test machines I have examined.
If your laptop did correctly display this border at one time, then we should be able to see this border again after starting from a new VI. If you create a new VI that contains an intensity graph and build this into an executable, does the border show up correctly?
As far as I can tell this is a bug in the intensity graph when it is a part of an executable built in LabVIEW 8.0. I have built your code into an executable in LabVIEW 8.2, and this border does show up correctly. I have attached both executables (in a zip file) so that you can compare their functionality on your machine. You will need the LabVIEW 8.2 Run-Time Engine to run the executable unless LabVIEW 8.2 is installed. Does this executable correctly show the border on your machine (as expected)?
It appears to me that this bug was corrected in LabVIEW 8.2. However, I was not able to locate explicit documentation of this bug being identified. As I mentioned, I will follow up with R&D to be sure that this behavior was known in LabVIEW 8.0 and intentionally corrected for current releases. I apologize for the inconvenience that this has caused. Please post back if I can provide any further assistance. Thanks,
Mike D.
National Instruments
Applications Engineer