LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How Copy a Program Correctly?

The easiest way to make sure you are getting everything is to use "Save for a previous version".

 

That will make new copies of all the sub-vis and dependencies. You might have to do a little cleanup because of the way it works but it's not that much.  

========================
=== Engineer Ambiguously ===
========================
Message 11 of 15
(326 Views)

Scrolling is not a good practice. I hate that for you! Whenever you get a diagram that one needs to scroll through like that I cannot help but think about the computer interface from the Jurassic Park movie where the girl flies over an interactive Island looking for the security control program.

 

Message 12 of 15
(318 Views)

@MontgomeryScott wrote:

Scrolling is not a good practice. I hate that for you! Whenever you get a diagram that one needs to scroll through like that I cannot help but think about the computer interface from the Jurassic Park movie where the girl flies over an interactive Island looking for the security control program.

 


I WISH!  I've inherited tons of these.  Usually from a coder who came from text languages and was forced into LabVIEW.  They start by making local variables for every control, then use a stacked sequence structure peppered with sequence locals.  Two or three of the frames contain the main program and it's 4 screens big.

 

Try to find the main part and separate it.  Then condense that down with proper LabVIEW (state machine, subVIs, Type Defs, etc...).  Then add back all the support code.

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
Message 13 of 15
(285 Views)

Personally I have a love / hate with labVIEW. I come from procedural text coding (no laughing) and I need to force my brain into the labVIEW thought style. sometimes I feel what could have been a few lines of code turns into a subVI with wires everywhere and a whole additional screen of crap. I also feel like "man I know how to do this, but now I gotta wire all this crap up, arrgh" BUT I also come from an electronics background and that lends very well to the schematic style of programming and I find myself navigating the interface a lot faster than I would with object oriented programming. Like I said, Love/Hate.

 

I'm pretty sure the Jurassic Park interface would be a Hate/Hate relationship after about 5 minutes. Kind of like the VR interface from that episode of "community"

0 Kudos
Message 14 of 15
(263 Views)

@FlybyWire wrote:

So we end up just copying that massive containing folder for the whole program over to a drive.  I can now view it in all its over complexity...think there's at least 30sub VIs in this thing and the main is so big you cant see the whole program with out scrolling miles...figured out ho to zoom out using ctrl mouse wheel and with it all the way out still doesn't fit on screen .  Thanks everyone for the help


There goes your "expert level programmer" comment. If it's only 30 sub-vis and a massive main it's probably bad. 🙂

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 15 of 15
(249 Views)