By Benjamin R
I'm implementing a tool to create brand new project based on a custom project framework that include LV code and build specifications. After cloning and setting anything up and running, I need to find a way to update the installer UpgradeCodes of the installer build specifications defined in my project.
I've tried some VIs from the AppBuilder or InstallerBuilder APIs (..\vi.lib\AppBuilder API and ..\vi.lib\InstallerBuilder) but nothing seems to let me change the UpgradeCode of an installer build specifications.
Does anyone know if there is a way to do so?
By Yaw Mensah
I have installed Labview 2020 on Dedian Buster using the rpm to deb conversion method via alien. Due to Architecture mismatch i deleted the *i386.rpm files before conversion.
My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option.
I will be grateful for any suggestions.
Thank you in advance.
This days, I meet a strange thing: The exe created by LabVIEW might be no-acitve status anytime when my customer use it to get current data from 6485 and product SN from a Bar code scanning gun then recording data by NPIO .Unfortunately I have a long time business travel.
My customer ask me to solve it -- he does not like using mouse to click the exe to active it.
Hence I want to use winapi detect my UI's status and make it activity.But it does not work well ....
When I click the desktop , the front panel will be as this status.The problem is that I still can't input keyboard.
Another: I find that the focuse threat should be the UI THREAT ,But I can't get this vi's threat by GetCurrentThreat().
(Cross-post from ni.com forums)
We have a LabVIEW application, which has a LabVIEW-based Installer. This LabVIEW installer is called from within another Inno installer (since our main Inno installer pulls together multiple components, most of them not LabVIEW). Whenever this Inno installer ends, it always asks the user to restart their PC, even if the LabVIEW installer was cancelled.
I narrowed it down, and it's reproducible with only the LabVIEW installer, so it's definitely LabVIEW installer's fault. According to Inno's help documentation, "if a program executed in the [Run] section queues files to be replaced on the next reboot (by calling MoveFileEx or by modifying wininit.ini), Setup will detect this and prompt the user to restart the computer at the end of installation." However, as stated above, this dialog is triggered even if the LabVIEW installer was cancelled and wrote no files.
Now, the above linked documentation refers to a flag I can put in my installer script to ignore this restart dialog, but it's a global flag, and I would like my other installers to still make use of this handy restart dialog if necessary. Unfortunately it seems LabVIEW installers trigger this even if not actually necessary.
Has anyone seen this before? Any ideas how to make my LabVIEW installer NOT muck around with the MoveFileEx or wininit.ini stuff if/when it's not actually needed? Attached is a LabVIEW project and Inno Installer script which easily reproduces the problem. To reproduce:
Extract the attached .zip Open test.iss in Inno Setup and click the "Run" button Alternately, just run the built installer under "\Output\test_inno_installer_126.96.36.199.exe" Click Next on 'Select Components' dialog Click Install on 'Ready to Install' dialog When LabVIEW installer pops up click Cancel, then yes (you're sure) See the Restart dialog Thanks!
I am facing issue in labview programming. My vi read csv file in a folder and plot it in waveform graph. Initially i have twenty csv file in that folder, while runnning my vi some more csv files will be added to that folder. The problem is only twenty csv file initially placed got read, later added csv files were not read by labview.
Condition: Once my vi starts running, the files will be automatically added to that folder. Because i am running an experiment which stores data in the form of csv file to that folder. How to keep on read the csv files continuosly while my experiments stores series of csv files.