NI Home > Community > NI Discussion Forums

LabVIEW Idea Exchange

Showing results for 
Search instead for 
Do you mean 
Announcements
We've turned on a search before post feature in the LabVIEW Idea Exchange. This new feature will help cut down on the number of duplicate ideas in this space!

The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!
New Idea
0 Kudos

I was trying to isolate two versions of code by putting them in a "Version 2.0" and "Version 2.1" library, and then (at run time) calling the appropriate analysis routine from the "correct" Library based on values stored in the data.  In the process, I managed to corrupt the .lvlib file, and (because I didn't know better) tried to "correct" this error by deleting the .lvlib file.

 

What that left me with was a file, formerly in the library, that I couldn't open without LabVIEW complaining bitterly that it could not find "Untitled Library 1.lvlib".  In addition, I could not even create a new Project and "Add" anything without such an error message appearing.

 

After a few weeks of struggle and consultation with NI Support, we found part of the problem -- the file that was formerly in the (now-deleted) Library had "hooks" to the Library embedded in its header.  Since this is in a proprietary (NI) binary format, I would like NI to provide a utility that can open a VI (or anything else that can be embedded in a Library) and remove the "hooks" that associate it with a particular .lvlib.  If this function were a LabVIEW function, then the user could write a utility using this function to apply it to a file, a folder, or a directory tree, as the situation warranted.  This would allow large VIs "corrupted" by being placed in, and improperly removed from, a Library to be returned to a stable, non-Library, state.

 

Bob Schor

0 Kudos

When we put a breakpoint inside a repetition structure LV runs the code inside loop before it stops. If we want to break before the 1st iteration we need to add a breakpoint outside the structure. The current way doesn't communicate the actions properly. I propose a slightly different way to communicate it:

 

Repetition Structures Breakpoint Better Indication.png

 

The left border acts as the outside border and the other three as the inside current one.

0 Kudos

Handling events from outside LabVIEW

Status: New
by Member m_m_m on ‎03-04-2015 04:26 AM

I would like to receive events that are generated by another program in LabVIEW executables. For example if another program tries to close my application with "CloseMainWindow" (see https://msdn.microsoft.com/en-us/library/system.diagnostics.process.closemainwindow(v=vs.110).aspx) it is not possible to react on that event and the application is closed immediately.

It would be great to receive such an event in the LabVIEW event handler to make it possible to ask the user if the application should be terminated, files saved, close openend ressources etc. (like the events "Application Instance Close?" (http://zone.ni.com/reference/en-XX/help/371361H-01/lvprop/app_app_exitq/) or "Panel close?" (http://zone.ni.com/reference/en-XX/help/371361G-01/lvprop/vi_panel_closeq/))

 

0 Kudos

Add "Text File" to the "New" pull-right menu in the Project Explorer window

Status: New
by Member RBXSystems on ‎03-03-2015 06:34 PM - last edited on ‎03-04-2015 09:50 AM by Trusted Enthusiast

From within the Project Explorer; it would be very useful to have the option to add a text file (*.txt) to the project, class or .lvlib.

At present the options are, as shown below:

 

LabVIEW_txtfile.PNG 

 

Adding text files will give the developer a simple method of creating documentation notes, that can be copied and pasted later.

 

[admin edit: updated title of idea to make it more clear that creating a new text file is the goal]

 

 

0 Kudos

Make LabVIEW look nice on a retina display

Status: New
by Trusted Enthusiast on ‎03-03-2015 01:13 AM

Retina displays on macs are really nice to work with, the details quality is a real plus, it would be nice if LabVIEW could take advantage of that, for now LabVIEW look really blurry & ugly on a retina display.

 

See the difference between LabVIEW and GitHub :

LV & git - no zoom

 

Zoom on LV :

zoom on LV

 

Zoom on GitHub :

zoom on github

Make it possible to scroll through the items within a picture ring using the mouse wheel.

0 Kudos

In Diagram Disable Structure, if there is an option provides "Selector Terminal" that could help to control programmatically. This could be optional selection in RCM (Right Context Menu).

 

Connecting Enable/Disable as Constant/Control to Case Structure would not do all purpose as the functionally of Diagram Disable Structure Enable/Disable individual does.

 

Diagram Disable Structure have unique behaviour if this Selector Terminal is given as optional that will add even more vale to the same.

 

As programmer myself felt that why do this be controllable, because while developing big codes we use to much of diagram disable structure , when we are suppose to change to Enable or Disable, I has to search for around my code. If this has controllable option that help to do my work even more efficient specially while testing code. 

yrfj.png

 

In LabVIEW 2014, sbRIO-9651 projects need a FPGA socket CLIP to be selected.

This FPGA socket CLIP can be user defined to select aspects like available FPGA pins.

 

By default, a user defined FPGA socket CLIP is saved in the National Instruments installation folder

or in the National Instruments user date folder. In other words, these FPGA socket CLIPs are not

saved with your LabVIEW project. This means you can forget to keep them by putting them under
configuration control (happened to me when my PC hard disk was changed) and other users will

not be able to use your LabVIEW project if you forget to provide the FPGA socket CLIP used
(happened to me when sharing my projects with NI engineers).

 

My suggestion is default behaviour of the CLIP generator should be changed.

This tool is used to select or create a sbRIO-9651 FPGA socket CLIP when creating a LabVIEW project.

I propose this tool should always save the created/selected CLIP under the project folder.

This would help to ensure the LabVIEW project contains everything associated with the project.

 

Optionally, it would helpful if the LabVIEW project dependencies showed FPGA CLIP usage.

I have unknowingly had a project using another's projects CLIP (especially when the CLIPs have

the same name).

 

Resizable ring and enum editor

Status: New
by Member TimGFellows on ‎02-26-2015 06:27 AM

If I have an enum or ring with lots of items, rearranging these items with the editor screen is a pain because it is fixed in size.  In particular, the table where we can reorder the items needs to be bigger.  Preferably, the whole screen needs to be resizable.

0 Kudos

Property nodes - write by default

Status: Duplicate
by Member TimGFellows on ‎02-26-2015 05:48 AM

In my experience, it is far more common to write to property nodes than read from them.  For example, I often enable and disable controls, but it is much less common to need to check whether they are enabled or disabled.  So when property nodes are created, could they be in "write mode" by default?

Find event cases

Status: Duplicate
by Member TimGFellows on ‎02-26-2015 05:39 AM

It is easy to find locals, references and property nodes of a control.  If I want to find all code associated with a control, there is one thing missing - the ability to find any event case associated with the control.

0 Kudos

Silver buttons

Status: New
by Member TimGFellows on ‎02-26-2015 05:34 AM

The silver controls are great but we need a couple more buttons:

  • An Exit button - perhaps with a graphic of a door on it
  • A Delete button - perhaps with a graphic of a trash can on it.

Any others that any readers can think of?

Indicator for typedef in array on block diagram

Status: New
by Member Trager on ‎02-25-2015 12:16 PM

The upper left corner indicator for type definitions on the block diagram is really useful, but that breaks down a little when you are using type definitions in an array. It's generally better to type define the element, not the array itself, but the array icon or terminal doesn't show anything to indicate that the contents are defined. How about putting the black upper left corner inside the bracket (for the indicator/control) or inside the frame of the icon? That would still show that it's an array, but would make it clear that the content of the array is linked to a typedef.

3 Improvements of the Table controls

Status: New
by Member G_Mulder on ‎02-25-2015 08:08 AM

The Table is an important UI feature allowing cell widths adapted to the contents (a bit like in Excel). That is much better than the rigid array front elements. It is also much more powerful since cells can be coloured, cell fonts can be changed, cells can be highlighted and still more. Some possibilities appear to lack:

 

1 There is no 1D version of it. This necitates the user to finely adapt the height to see only one row. This makes that no dark grey line is around it and a user can accidently change to lower lines by selecting a cell and some mouse operation. It is hardly possible to return backward, certainly if the user is not aware that the line is in reality a 2D field.   Under properties e.g.' 1 row, 10 columns' can be given, but that does not prevent changing to other rows. For arrays dimensions can be added (from 1 to many), for the table dimensions 1&2 would be helpful.

 

2 Cells can be indicated with help of the properties 'selection start', 'selection size' and 'selection color'. The selections can not be programmatically disabled and re-abled when needed. At least a corner element remains if the 'selection size' is reduced to (0,0). With the right-click menu options a 'show selection' option exists for enabling and disabling the feature. It lacks as a property node.

 

3 Cells can be coloured with help of property node calls, what is nice. The method to undo all colourings and other settings does not exist. The invoke node method 'reinit to default' has no influence on the individual cell fonts, cell colours, etc. An invoke node to reset these features is wanted as well in addition to the existing reinitialisation. This lack is preventing using these features since the changes should be kept in memory somewhere to undo, or all cells have to be overwritten periodically with a lot of code. If the table length is undefined since e.g. measurement data  is put into it, then an arbitrary number of rows have to be assumed. A reset function can take this trouble out of hands.

 

The same remarks hold probably for the listbox controls.

0 Kudos

NEW feature wanted - idea of the new control

Status: New
by Member vlapet on ‎02-25-2015 04:04 AM

Hello would be good to have Integer number in the BINARY format switched with clockwise description of the bits.

See you VlaPet

Support Fixed-Point (FXP) Data Type in Unit Test Framework

Status: New
by Active Participant James_McN on ‎02-24-2015 11:20 AM - last edited on ‎02-24-2015 01:11 PM by Trusted Enthusiast

I have been using unit test framework testing for FPGA code (although you do have to manually bind everything!)

 

This would be significantly easier if unit test framework would support fixed point numbers, currently I have to not test or create wrappers for much of the logic.

 

[admin edit: updated title to more clearly reference FXP data type]

I have recently been using more test vectors in the unit test framework.

 

The principle works well but if you are in a unit test and decide you need a test vector you must:

 

  • Close the unit test configuration
  • Create a test vector
  • Set up your vector (entering values and data types, which is much easier if you could see the actual unit test case)
  • Close the vector configuration window
  • Open the unit test configuration
  • Assign the new vector file to the unit test
  • Now you can assign vectors to test inputs

This seems convoluted and forces unnecessary context switchs.

 

I propose that at a minimum, you should be able to create a new vector file and launch it's configuration without leaving the unit test configuration window. I suspect that the whole process could be streamlined even further though.

0 Kudos

Set "Context Help" using VI Reference

Status: New
by Active Participant PhillipBrooks on ‎02-24-2015 07:09 AM

Add a LabVIEW application method or property that would allow us to set the object of the context help so that we can specify a VI from a tree based browser (much like the Project Window does).

 

https://lavag.org/topic/9167-context-help-for-a-vi-without-loading/?p=54820

 

0 Kudos

For loop start from a different index

Status: Duplicate
by Member BuoNI on ‎02-23-2015 10:50 AM

I mean when it's used for indexing array...

It could be really useful if someone wants to skip some initial indexes...
It has already been done?

0 Kudos

Short Cut for VI Analyzer

Status: New
by Member sandyy on ‎02-23-2015 05:07 AM

Short cut for VI Analyzer makes more handy ?

 

Cnt + shift + Q - Something like that :-)

Latest LabVIEW Idea Exchange Blog Posts
About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
Idea Statuses