I have created an app that works without issue. Takes a file, parses the file, and creates a new file. Depending on the file it is fed, it may call a different parser (there are 2 parsers internally, potential for more). But, it works without issue in Dev Env.
What does "work without issue mean?" Well, I'll tell you. As a VI in LabVIEW environment, I feed it all the different files and they are correctly parsed and the correct file is created. As a built executable, I feed it all the different files and they are correctly parsed and the correct file is created. As a DLL called by Python, 1 of the parsers work... the other just freezes.
The issue does NOT lie with Python as it's just feeding it the filepath and getting the finished filepath as a return. Why is this not the issue? Cuz it makes no sense for that to work for 1 and not the other. Again, all files have been tested against the executable version and the VI version.
There's something LabVIEW to DLL that Windows, or RTE, or something doesn't like. Are there any special considerations that need to be kept in mind when building a VI that will be eventually made into a DLL? Like FPGA? You can't use the entire pallet when making FPGA.
Things I am using: Data Value References, Queues, FGVs. But both parsers use these. The only significantly different thing about the parsers, one parser runs two loops asynchronously.
