todd

Not enough information. If you do not have access to the python source (because they used py2exe/PyInstaller), find the device's programming manual.

How does the python script communicate with the device? pyVISA?

Wouldn't hiding the FP be good enough? Minimize it behind the BD's icon view - without leaving the FP's window in the taskbar list.

First of all, this thread pretty much makes me want to vomit all over my keyboard so I take it in small doses.

I'll take vomit any day over some of the code I've been lucky enough to deal with.

You discovered the mouse-overs?  Sounds like you were one of today's 10,000

 

Relevant XKCD

 

A bit of a stretch but I wanted to see if I could find one.

Definitely was one of 10,000 - but it was a few years ago.

-- Doing my part to be one of the 10,000 every day.

Help -> Find Examples -> Search -> 3D -> solarsystem.vi

As is oft the case with xkcd, the mouse-over text is perfect.

I had to go back through ALL of them once I "discovered" the mouse-overs.

"When all the world recognizes beauty as beauty, this in itself is ugliness"

With a project folder containing rougly 850+ vis, lvlibs, and ctls, the project-based conversion dialog says it's at 6736 loaded and counting. I would love to know what is going on here. I assume this is enumerating the files, removing the compiled code, and saving them?

I'm working on doing the same thing with a project that sounds similar to yours. The thing I'm worried about is having all of the typedefs in memory along with all of their callers - many of which are ACBR. Over the next couple of days I'm hoping to get a little script together that creates a tree.vi to keep everything loaded.

Thanks for sharing. Congratulations on 50 posts!

Thanks, Jordan.

Just to follow up on the security aspect, I learned that the keywords are along the line of "What is the 'at rest' state of my data?" One way to think about security is to consider whether the host is HIPAA-compliant. Those hosts charge plenty, though, and typically don't have all the features of SCC, issue-tracking and FTP-like functionality.

The hosts I've looked at so far don't allow the repos to be hidden from the hosts' admins. Does anyone know of a "secure" hosting solution?

Here's the cross-post on NI's forums:

http://forums.ni.com/t5/LabVIEW/What-is-the-most-important-difference-between-3D-Picture-control/m-p/2550677#U2550677

What about the registry? Procmon lets you filter on "Process Name" (<yourapp.exe>) and "Operation" (RegQueryKey). Dropping a single File Dialog on a blank VI and running it shows lots of key queries - not that they're all related to File Dialog...

Honeypot approach. Nice!

I tried suggesting something like this some years back to "keep out the riff-raff" and let the As in LAVA have at least some semblance of meaning. The suggestion wasn't met with too much enthusiasm.

I remember that thread. People got hung up on keeping out people who want to learn. How about multiple choice:

What is the format of LabVIEW's registration key:

a) A12B34567

b) AA123B4567

...

Ok, support-side: the one that actually wasted my time (instead of allowing meditation, as Rolf mentions) was making sure all the wires had their bumps on the same side (scalar string, scalar path), smooth-edges instead of bumpy edges (1D array of string, path, etc), and on and on. BD's are usually small enough that "Horizontal Gap" doesn't come into play much anymore.

Name the constants and create a QD plugin that aligns the selected VI with the left of the "left-edge" constant, and the bottom of the "bottom-edge" constant.

That's totally OCD!

 

However, why the unnecessary bend on the Event Reg wire? Let me guess, it lines up with the top terminal of your VIs inside the case-structure?

Close: the output of the event structure and while loop lines up with Unregister for Events. I've started putting the event registration itself in Actor's class data so it can be unregistered in Stop Core. Now I can get rid of that bend!

I'll see your scrolled-case-wires-don't-move and raise you my scrolled-case-VIs-and-controls-don't move. The empty string constants in this BD are used for aligning edges of nodes in the cases:

Oh, now I notice that you mentioned functions.

Once in a while I'll download VIs from NI forums. I have to make sure I have not had any coffee, yet, otherwise I get sucked in to the vortex of cleaning up ALL of the code.

Straight error wires with non-hidden bends. The nudge-to-check-connection also works for putting the 1px bend in the horizontal middle of the wire.

Has anyone mentioned having to line up all the input and output terminals of case and event structures, and for and while loops? That one slows me down a little, sometimes.

http://zone.ni.com/reference/en-XX/help/371361H-01/lvconcepts/resolving_project_conflicts/

Just adding the cross-post link:

https://decibel.ni.com/content/message/57754#57754

(And watching for good ways to do that data sharing. I've done it poorly, already, including sharing a DVR with two copies of a data class - one in producer and one in consumer, each with their own index.)

I vote for the lvclass, ctl, lvlib and vi files to be "locked-no password" during the Post-Install Custom Action in VIPM (or VIPM pro has a checkbox that does this).