Search the Community
Showing results for tags 'ini file'.
Hello all, My question is: what is your preferred non-volatile way of storing daqmx task configurations? Backstory: For a long time I've used ini files to maintain task configurations between executions of a program. This has worked for primarily static DAQmx configurations but I'm looking at creating a test executive with some degree of flexibility, which means daqmx task configurations start to get more complicated. If you use MAX for storing your tasks: Do you run into problems accessing and maintaining these tasks even though you don't have direct access to the file? Or i
Hi, When an Exe is built using application builder, an ini file is created in the same location as that of the Exe with the same name. This ini file contains some settings to be used by the Exe and is read by the Exe whenever it is run. There is an option to specify the ini file using the command promt using the command line argument 'pref'. A shortcut may also be used for the same purpose (as explained in the Labview wiki). The settings are read from the specified ini file by the Exe. Everything is fine until "Pass all command line arguments to application" option in the 'Advanced' catagory