LabVIEW Idea Exchange

Custom probes are great, however unlike the default probes you do not always have them with you...so why not just make the default probes just a tad smarter? 

- The array probe e.g. should not just show a single cell - it should by default show at least some of them (1*10 for 1D, 10*10 if 2D etc. e.g.), have it's scrollbars visible and be resizable?

 You could add some core information about the array, like it's size e.g. in an indicator on the top as well....and perhaps have a pull-down menu for the display format. Keep it general and simple of course, but a bit more convenient than today's probe.

- The string probe should also be resizable and have a control that let's you switch the display format.

- etc.

The property node has two major advantage over LVOOP - it allows placing a lot of function calls in a horizontally limited space and it uses text, which is MUCH clearer than small icons (IMO) for something like this. It would be nice if LVOOP had support for this as well.

The implementation I'm thinking of is basically having VIs which will be marked as property VIs (similar to what XControls have) and will only be allowed to have a single input (or output) other than the class and error I/O. These will appear in the list when you connect an LVOOP object to a property node (ideally with the properties from the parents as well), somewhat like this:

When you run the code in this image, LV will run the VIs sequentially, passing the object and error I/O from one VI to the next.

I know that NI already tried to do this in the past, but didn't finish it. Hopefully, enough support here will encourage them to pick it up again.

LabVIEW classes are how you create new data types in LabVIEW. But part of being a new LV data type is having a front panel representation. Although users can write XControls for displaying their classes, and they can put those XControls in the palettes, whenever a user of their class chooses "Create Control" or "Create Indicator" for the LabVIEW class terminal, they get the cube display. In order to really add a new data type to LabVIEW that behaves as well as, for example, the Timestampp or the Waveform, there needs to be some way to associate a class with an XControl and say, "This particular XControl should be used as this class' default control/indicator whenever one needs to be built."  (To prevent infinite recursion and load dependency problems, whenever you did Create Control/Indicator on a member VI of the class, users would still get the cube control/indicator.)

I think structures should have a better label system. Currently I use free labels of the same color as the loop which looks great and makes the code easy to read and debug. But if I resize my loop I have to manually resize the label as well. I think this should be built into a right-click option.

(structure) rick-click » visible items » Structure label

It would be useful fo have a built-in mechanism for protecting executable code.  Essentially something similar to what labview uses to protect its own code.  When an executable is run (if this option is selected in the build) the registry is checked for a licence key, the key will compare the hardware id (could even look at max for serial numbers) and key and see if it decodes to the selected seed specified durring the build process.  If the key is not a match the user can not use the program.  Although this is not all that difficult to add, implemented it into the build only would keep for extra code in the source and spending time to protect your IP.  I have been asked many times for this by my clients and hate to have to spend extra time building this feature into my applications.

Summary:

Builds have Licence tab.  Includes a private key, enable liscence on exe, liscence expiration (optional), Custom Licence  message(optional ie: "please contact xyz123.com for a liscence number HardwareID=111112345")

If enabled, the licence key (stored in registry or appdata file) is checked.

If key is valid continue loading exe, else prompt for licence key to be entered with custom message.

If LabView is to be used as an endproduct with 1000's of distributed copies of your application, the IP Protection is a must.

I know there are many 3rd party products but one specifically integrated into the LV runtime environment would be very cool.

\

It would be nice to have bookmarks (possibly based within the project) so that you could quickly jump to certain areas of your code that has to be modified or reviewed frequently.  Obviously, things like state machines are self documenting, but it would still be great if you could quick jump to certain areas.  Being project based, you could also jump to any bookmark in a subvi.

Currently, when you use the Reshape Array primitive, if new elements are created, they are filled with the default data of the datatype. Alternatively, allow a terminal that defines the fill value.

CVI has Notify an option in Range Checking; I’d like to see LabVIEW to offer such option in Response to value outside limits.

-Coerce

-Ignore

-Notify