Jump to content

Search the Community

Showing results for tags 'ini file'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 3 results

  1. I need to use 5 Bytes Hex string as a key, Hex string as a Value. Normally data stored in INI as ASCII. What can be the possibilities to store HEX String?
  2. 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
  3. 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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.