LabVIEW Idea Exchange

The default LabVIEW environment option should not show terminals as an icon. 

Typical question in development process: "How quickly does my code execute? What runs faster... Code A or Code B?" So, if you're like me, you throw in a quick sequence that looks like this:

AHHH! What a mess! It's so hard to fit it in, with FP real estate so packed these days!

We need this:

 Just like my other idea, and for simplicity's sake NI, I would be PERFECTLY happy even if you had to set up the probes during edit mode, and were not able to "probe" while running.

 As a bonus, this idea may be extrapolated into n timing probes, where you can find delta t between any two of the probes.

Here's something that makes FP design difficult: shadows behind floating objects on FP. Add an IDE preferences option to disable shadows.

NOTE 1: The default is for shadows should be enabled. This is a handy feature that alerts a new FP designer that something may not be right with the arrangement.

NOTE 2: This does not apply to the BD. I think you should ALWAYS correct objects floating over structures on the BD.

NOTE 3: Give us an option to "Show Floating Objects." Like Show Buffer Allocations, SFO would flash the floating objects. Alternatively, give a list of floating objects (this should work on BD and FP)

If you write a multi-purpose sub-VI, it is sometimes desirable to know during run-time, if an input of the sub-VI is connected to some source inside the calling VI or not. E.g. if you have two inputs and you want to do a certain action whichs depends on which input is connected, you have to write a polymorphic VI. Therefore you have to write at least 3 VIs: one VI for each input and the polymorphic VI. With a new control property or method, which tells you if the input got it's data from some source, you could do this with just one VI. There are of course other scenarios where this new feature could be useful.

Regards,

Marc