I would like the vi metrics to record the time spent on programming individual vi's, broken down into seperate operations: cleaning block diagram, writing code, drawing icons etc. The function should be able to stop recording when someone is not working with the vi. Ideally time spent on other programs while the project or vi is opened should not be recorded.
I like to collapse long string and path constants to consolidate diagrams. Showing the string or path value in the tip strip is useful but tedious to update.
I suggest an appearance property that would automatically display the current value in a tip strip for string and path constants.
This property would be most useful if the Block Diagram Options page was also modified to allow a global setting.
The seperate views are great. This would be more useful if we could view items and files at the same time
[admin edit] Clarified title of post, and removed comments below related to clarifying the title.
I was using quick-drop today and I had an idea to yet further augment the insane efficient of this tool...
A) Display the Quick-Drop dialog box when a letter or number is pressed on the block diagram instead of CTRL+Space. Letters and numbers don't do anything unless you're typing in a comment, constant, etc. This would eliminate two keys from the process.
B) Select the best Quick-Drop match with a right-click while the dialog box is open. The right mouse button does nothing in this dialog box at the moment. This would eliminate the motion to the Enter key and stay over the letters / numbers with my left hand.
If I have "g" assigned to "Greater?", all I would need to do is press "g" and right-click. BAM. DONE. The original method would be CTRL+Space, then press "g", then press Enter, and then I'd have to move my hand back to CTRL+Space for the next combo.
I know it seems small, but I use Quick-Drop HUNDREDS of times a day. What do you think?
LabVIEW users should be able to deploy programs to the Intel Edison Module
The Intel Edison is a very small single board computer with a dual-core Atom processor, 1GB RAM and built-in WiFi/Bluetooth LE.
Functionality can be added by connecting breakout boards, so called blocks. Many of these blocks are already available, like ADC, GPIO, Arduino, PWM...
In my opinion the Intel Edison is very well suited for stuff like embedded control, robotics, the Internet-Of-Things, and.
Thats why I posted this idea to convince NI to support it in LabVIEW!
If we select some code and try to copy it to the front panel, nothing happens of course because the code has no meaning on the front panel.
However, we can paste that same code into many other applications (e.g. MS Paint) and it turns into an image. We can immediately copy that image and paste it to the front panel. I often use this for forum examples, e.g. here.
Why can't we eliminate the middleman????
We should be able to paste code directly to the front panel and it will simply turn into an image of the code!
We should even be able to simply drag code from the BD to the FP for the same effect.
This could even be useful during code reworking. We could temporarily paste a picture of the old code to the FP so we can better remember what was connected where while we make modifications.
(It could even turn into a snippet so we can drag it back and it turns into code, but a plain image is probably sufficient)
Sometimes I would like to shift some nodes inside an event or other structure. Currently I have to either redraw the structure to include the nodes (have to reset tunnel/shift register assignments etc, doesn't work for cases) or move all the nodes inside the structure and rewire everything.
Proposed solution: resizing the structure with shift pressed includes the nodes inside the structure, much like if you draw the structure around the nodes in the first place. Also this feature would be super helpful for adding frames in a flat sequence, just shift and drag yourself a new frame with everything inside.
Probes are useful for seeing when a piece of code has executed for the first time after clicking 'run' as well as to see real-time values on wires.
Currently probes retain their values when the top VI stops, which is useful, but less usefully, keep their values indefinitely, even when the VI is restarted.
I'd like them to reset to 'Not Executed' when you click 'Run' again, otherwise I have to delete and recreate each probe in order so that I can tell when they have executed for the first time (unlike the lightbulb which slows everything down, breakpoints which pause the code or adding indicators which may not be convenient on a front panel (and require initialisation code)).
If this could be implemented (or could be an option for all probes or for any individually by right-clicking on them) I would find it really useful!
Sometimes I have to turn on some front labels of controls or indicators to see what the names of them are. It would be nice to have the
label name show up in the help window as you hovered your mouse over the controls and indicators.
Just a thought...
I was looking for a smart way to bind more than 1 key to a button.
I thougt about the menu "Advanced" -"Key Navigation". The selection there is only possible for one Key per button.
If you want more keys modifing a button you have to implement this, using an event structure etc....
So the idea is as shown in the picture below:
You could add Key bindings for buttons to multiple Keys.
It should be nice to be abble to use the LabVIEWObject class in order to create Generic Collections. (List, Heap, Stack, Dictionnary, Hash Tables ... )
In all Object programming langages it is possible to access the "Base Class" (Object...), this feature should also be available in LabVIEW Oject.
Thanks a lot.
[admin edit - clarified idea title]
This idea exist certainly, but i don't find it ... so sorry if dupplicate ...
For the moment, the default probe for LabVIEW object is a string containing the "Class name" ... quiet poor !!!
By default, the object probe should view the content of the object data type !
Thanks a lot.
When placing a diagram disable structure, the 'enabled' side of the structure starts blank, and the wirethroughs are replaced with default values. I have never wanted this behavior. Every time, I want it to:
1) duplicate the disabled side to the enabled side
2) select everything in the enabled side except for the wires.
3) execute the 'remove' function I normally get by 'ctrl-space, ctrl-r' (quick drop, remove)
I misunderstood ouadji's post here, but I liked my interpretation of it. I didn't find it on the Exchange so...
Make it possible to copy the VI properties from one VI to another.
User right-clicks on the VI in question, selects "Copy VI Properties", then right-clicks on the new VI and selects "Paste VI Properties". BAM! All (or almost all - to be discussed) properties are copied to the new VI.
Similar to JMP's Copy Column Properties:
What properties would be copied over?
Initally, I thought EVERYTHING! But then my fit of insanity passed and I realized that some items should not be copied.
The Big Two That Shouldn't Be Copied (that's like, my opinon, man...):
Everything else is up for debate. So go, debate away you master debators!
This an extension to the idea which I have submitted.
I had difficulty when accessing the control names on the front panel have more number of controls and also when we have same control names in the different pages of Tab Control.
It would be good if they can be grouped by Tab Page under the Event Sources in the Event Structure as shown below. This is similar to what the LabVIEW does when displaying the Cluster Variables in the Event Sources.
It will be helpful it the idea can be extended where ever accessing the controls/Indicators from the Tab Control Pages.
In the block diagram, it would be helpful if LabVIEW can display the full link or name of tab page when accessing the local variables . This is very useful if we have multiple controls with same variable names on different tab pages.
I am not sure if there is any idea submitted on this, I could see idea which I had thought of adding.