Jump to content

Search the Community

Showing results for tags 'current value table'.

  • 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


Location


Interests

Found 1 result

  1. First off, thank all y'all for schooling me on Data Access Best Practices and FGVs, Action Engines and DVRs. Now let's dumb it down a bit. I want to ask about good(?) old-fashioned native Labview globals. Here's a use case: A control program for an industrial process has 10-20 adjustable parameters (numerics and booleans) on its GUI. These parameters are written once at program start based on values in an INI file, and then an arbitrary number of times thereafter when the user changes them. It is not critical for the process to update the user-changed value at the exact millisecond. So: globals? Or what? How lazy can I be, before the expected value of time and effort goes negative? Let's assume that the control program is subject to revisions such as adding more adjustable parameters. The additional parameters could represent new hardware that has been added, or simply taking advantage of more functions (that we had thought we could just set and forget) of existing hardware.
×
×
  • Create New...

Important Information

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