Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/10/2016 in all areas

  1. The attached VIPM contains an extension of Messenger Library that is intended to add extended functionality to controls/indicators, via a background process that is launched and which registers for the events of the control (the background process is a Messenger-Library “actor”). This is meant to be an alternative to XControls. Included are two “Augments”, both with examples. See <examples>/drjdpowell/UI Augments/Examples/EXAMPLE Twin Cursor Graph Augment. This takes any graph with two cursors and draws a line between the two and displays summary info of the data between the two cursors: There is also a cross-section plotting for a 2D intensity chart: This package is in LabVIEW 2015, and requires Messenger Library (latest, in the LAVA-CR) and JSON LabVIEW and Shortcut menu from Cluster (both in the LAVA-CR). drjdpowell_messenger_ui_augments-1.0.0.8.vip
    1 point
  2. Nope, I actuallly use LVOOP. Still dont like it though. Just being facetious :).
    1 point
  3. You can actually extract a VI from an EXE, but there is a very good chance it won't be useful at all. If you did not enable debugging when the VI was made then you will get a VI with no block diagram, no front panel (in most cases) and no source code. This VI will be a thing that can be ran, but only in that one exact version of LabVIEW it was made for. There will be no VI icon, no description, and possibly no terminal labels (it's been a while since I've done this so I can't remember). This process of pulling a VI out is not like a decompiler. The output isn't like source code, it is more like a DLL that is still binary and still compiled for a specific platform and target. tldr; what infinitenothing said.
    1 point
×
×
  • Create New...

Important Information

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