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.
I faced to delete multiple elements form the array which is having 20 steps.
if able to select multiple elements by holding the shift key we can delete selected items 1 time and can insert 1 time.
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.
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.
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:
Picture says it all.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.
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:
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.
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.
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:
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)
This idea directly comes from this issue : http://forums.ni.com/t5/LabVIEW/Issue-when-using-S
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 !
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:
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:
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.
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.
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.