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

Expose "Call Chain" as VI Property

Status: New
by Member TurboPhil on ‎07-24-2015 10:16 AM

The only way I know of getting the call chain of a VI is with the Call Chain primitive, which only works on *this* VI (the VI calling the primitive). It would be nice to expose that as a VI server property, so we could get the call chain of any VI by reference.

 

callchain.png

List out number of coersion dots in the vi

Status: New
by Member thilprakash on ‎07-27-2015 08:05 AM

List out number of coersion dots in the vi like a break point manager window.

Improving NI Example Finder

Status: New
by Member ReimarSpohr on ‎07-24-2015 02:51 PM

LabVIEW could highly profit from improved access to examples. I suggest to outsource the NI Example Finder to an advanced web search engine.

 

 

Problem:

I faced to delete multiple elements form the array which is having 20 steps.

 

solution:

if able to select multiple elements by holding the shift key we can delete selected items 1 time and can insert 1 time.

 

 

Array element.png

 

 

Search for Keywords is presently limited to logical "OR" search. It would highly profit from logical "AND" Search.

Path Control Disable Text Entry

Status: New
by Trusted Enthusiast Trusted Enthusiast on ‎07-07-2015 12:12 PM

If I have a path control on my front panel for the user to interact with, I will always show the browse button.  This button makes selecting a path easy from a user perspective, and from a developer I know that the path they selected has some level of validity.  So for instance I know that the path they selected must exist and be a valid path otherwise Windows won't let them select it, and the value change won't be triggered for the control.

 

But the user can manually type in text into the path control, and when focus is taken off the value change event will take place.  The problem with this is the path they entered might not be valid, or may contain characters my platform doesn't support.

 

I doubt a user will manually type in text in the control often, they will use it as an indicator showing the path they selected using the browse button, but on the off chance that they type somthing and it isn't valid, my code might crap out throwing errors.

 

I can add code to check for a valid path, and I can add code to check for illegal characters in the path, but I'd have to do this for every path control on every UI the user sees.  I could also write an XControl for this with a decent amount of work and hopefully meet my needs, but it would be nice if this were a native feature.

 

So what I'm suggesting is that the path control have an option, possibly in the browse options dialog, which makes the interaction with the control, only available by using the Browse button.  This would ensure that any value change event will be from the user picking a valid path with the browse button.

LabVIEW Version conversion tool

Status: New
by Member patibandla on ‎07-20-2015 12:07 AM

Hi All,

 

I saw in the Forums,Developer are spending more time on the convertion of the programs from UP to Down or Down to UP due to their requirment.

if NI provides the add on tool for Converting Up/Down,Down/Up.

 

it is easy to use and they can spend more time on other part of Developmnet.

 

Version tool.png

Allow project explorer window to be pinned

Status: New
by Active Participant ToeCutter on ‎06-29-2015 05:58 AM

I have a large library of general purpose functions and I do a lot of OOP in LabVIEW, and as a result my preferred workflow involves dragging a lot of functions from the project explorer window onto the block diagram. This workflow is slowed down, however by the fact that the project explorer window is regularly hidden by other windows when I click on them.

 

What I would like to see is something like most development IDEs have, e.g. Visual Studio, where I can have the project explorer always visible in a fixed position on the screen. I suggest this would be an option, so would not affect those who like things the way they currently are.

NI send us the NI Developer Suite each year on DVDs all packed in a nice little NI branded dvd carry case. We are on the SSP suscription and we receive 3/years, which means I have a whole stack of them.

 

I suggest that NI start shipping USB keys instead. USB has several advantages:

 

  • USBs are smaller
  • USBs are more usable on devices without DVD player
  • Installing with one large USB means no more DVD swapping. I can go to lunch while NI installs/updates without having to change the DVD every couple of minutes.
  • USBs are reusable: when you get a new version on LabVIEW on a new USB, you can use the old one for regular usage. This also means less waste, since the USB keys are still in use after a new version ships, but the DVDs are useless.

 

Ship developer suite on NI USB keys

Picture says it all.

 

Concatenate with an option of 'concatenate to new line'

 

 


I am not allergic to Kudos, in fact I love Kudos.

 Make your LabVIEW experience more CONVENIENT.


View and modify splitter hierarchy

Status: New
by Active Participant dsavir on ‎06-17-2015 03:01 AM

I use Splitter extensively to create resizable GUIs. However, if I create my resizable GUI and then my customer asks me to add parameters in a new pane on the left, I can't add to an existing GUI a splitter in the top of the hierarchy, i.e. a new vertical splitter that all the existing splitters will be on the right of the splitter and a new empty pane on the left. Any splitter I add will be added to the bottom of the existing hierarchy, and there is no way to change this. So to do this I basically need to rebuild the GUI again from scratch.

 

Another example, if this is my GUI:

scope.PNG

I can't add a status bar now, as any horizontal splitter I add will be inside an existing pane, and this can't be modified. However, if this idea were implemented, I could View splitter hierarchy and create a new horizontal splitter at the top of the hierarchy so that I would have my status bar without rewriting the whole thing.

 

 

Thanks,

Danielle

 

Close Project

Status: New
by Trusted Enthusiast on ‎03-21-2015 02:03 PM

 

 

  It would be very usefull to know which VIs are still running.

   aaaa.png

 

for connecting the Controls & Indicator very diffcult for more connector in the pane . 

 

if automatically zooms the pane while placed the wiring tool on the connector pane the programmer can easily wire the pane with the controls and Indicators.

 

Connector Pane Zoom.png

Try this:

  • Create a new VI with a numeric control on the FP and an event structure on the BD
  • Add an event case for "ValueChange" on the numeric control
  • Run the VI and click inside the numeric control
  • Press "Return" (or "Enter")

Notice that this does *not* trigger the value change event. However, editing the value and then pressing enter triggers the ValueChange event.

 

Ahh, but you point out "Well, in that case, the value *did* actually change, so that's why the event fired." And you're right.

 

But then try this:

  • Change the value to some arbitrary number, say "1234"
  • Observe that the ValueChange event fires
  • Now, highlight the numeric text and retype the exact same value: "1234", then press enter
  • Behold! This time it triggers a ValueChange event Smiley Frustrated

 

Seems super minor, I know. But I found myself in a situation where I want to trigger an event if a user hits "enter" in a numeric field, regardless of whether the value changed or not (e.g. it should be able to reassert the current value). Yes, the obvious solution is to handle the enter key press separately, but that means when the enter is used to assert a different value, I end up with *two* events.

Should be able to specify tolerance instead of just upper and lower limits. This de clutters the application block diagram when you are checking for a value within certain limits.

 

 . Upper limit becomes : x+ tolerance, Lower Limite becomes : x - tolerance when using tolerance instance of the polymorphic vi.

 

For even higher level functionality , specify units of tolerance : absolute, percent(1e-2), parts per million (1e-6), parts per billion (1e-9)

Open or Give more options on HTTP VIs

Status: New
by Active Participant zyl7 on ‎07-23-2015 08:23 AM

This idea directly comes from this issue : http://forums.ni.com/t5/LabVIEW/Issue-when-using-SOAP-requests-with-HTTP-POST-function/td-p/3169229

 

More and more devices are equipped with embedded webservers. And some of them require more controls HTTP protocol capabilities.

It would be nice to give the access to these VIs diagrams or to give more options set header fields !

Project Explorer: Hovering over a Virtual Folder during Drag & Drop should open that folder

Status: New
by Trusted Enthusiast ‎06-05-2015 12:50 PM - edited ‎06-05-2015 12:54 PM

In the project explorer, dragging an item into a folder opens that folder AFTER the drop. This is annoying. But I digress...

In fact, what would be useful is to have the behavior of the two file explorers I am familiar with (Windows and Mac OS), that is:

 

- if an object is drop onto a folder icon, the folder does not open (see link above)

- if the object is held for a while over the folder icon, the folder opens

 

This is particularly helpful if the project explorer has a hierarchical structure of Virtual Folders:

 

Screen Shot 2015-06-05 at 10.44.15.png

If I drag Untitled 1.vi over the Action folder and hold it here for ever, nothing happens, and in particular, I can't access any of the the subfolders.

After dropping it, I get this:

 

Screen Shot 2015-06-05 at 10.44.40.png

 

Now the top folder is open, but the VI is nowhere where I want it to be and I need to repeat the drag & drop action.

 

This example doesn't do justice to the real issue which is that for large lists of VIs and folders in a project, this becomes a real problem, as VI and target folders (after everything is opened to provide a clear path from original to target destination) may end up separated by large amount of space in the project explorer and you now have to use the temperamental "Drag the object over the 1-pixel wide location at the top of the project explorer to trigger scrolling" feature in order to slowly bring the object to its remote destination.

LabVIEW Free online IDE for Learner

Status: New
by Member patibandla on ‎07-17-2015 05:28 AM

Hi All,

 

Now a day every where cloud computing is bomming. if NI provides the LabVIEW Free online complier. 

people who does't have any setup .they can learn any where through Internet and NI cloud.

 

 

This will helps to more people to learn labview beginer  easily.

Sandboxed execution

Status: New
by Member spatry on ‎07-10-2015 11:00 AM

It would be really nice is the IDE, and my program were not the same process.

 

Especially when dealing with 3rd party DLL's, it would really be nice if a bad pointer or misallocated buffer in a DLL didn't crash my whole development environment, but instead just took out the running program.

I just had a case today where I had an existing wire (An array of configuration parameters) and I selected the wire and then tried "Create Sub-VI" on it.  Nothing happened.

 

Perhaps it would be simply consistent behaviour if we then allowed creation of a simple VI with Wire Datatype in and out with input terminal connected to output terminal.

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