Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/17/2014 in all areas

  1. Has anyone actually configured Git to work with LVCompare or LVMerge? (I've seen some threads on various boards saying it "should be something like" <x>, but it isn't quite <x> and I haven't found anywhere that someone has actually described it successfully.) Notes: I know how to configure TortoiseSVN to work with LVCompare and LVMerge. My new employer is moving to Git (some good, some bad in that, in my opinion, but that is another topic). I have been using Git for a few months now with reasonable success and decided I should try to set up graphical differencing. [OK,
    1 point
  2. You would lose the linkage to the typedef. Also I'm not sure how LabVIEW would handle changing the control from a typedef to a control, it may very well mutate your constant values just as modifying the typedef would. Of course case structures completely throw a wrench in the plans I've mentioned above. Fun fun fun.
    1 point
  3. This has been filed as CAR 455443 see this thread: http://forums.ni.com/t5/LabVIEW/Chart-Redraw-Issue-with-Multiple-Plots/m-p/2755616/highlight/true#M812948
    1 point
  4. Sure - you can save off portions of, or the whole, DAQ configuration in MAX (export to an *.nce file), then reimport it on the new system, either by using the MAX import feature, or programmatically in your LabVIEW code (there's a MAX API under the DAQmx palette somewhere). One relatively unknown feature is that importing *.nce files doesn't (have to) over write all of your MAX settings, so, if you have an architecture that reuqires it, you can load several *.nce files as you progress through your system setup (we use this technique in modular and scalable architectures that are build to run
    1 point


×
×
  • Create New...

Important Information

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