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.
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!
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)
When dragging a control / indicator label or caption, if you move within a certain distance from the owning terminal the label will snap to one of a set of given positions (top-left, top-middle etc). Outside this distance (or if the user presses the spacebar to toggle this behaviour), the label can be freely positioned.
The selector terminal for a polymorphic VI should display the same behaviour with regard to the owning VI icon. A polymorphic selector is currently always free-floating.
PS : Many thanks to Intaris and TiTou for their help to formulate this idea.
I like to compare two build specifications of two different projects.
To do this it would be very helpful, that the build specification dialog box is not modal and that i can open each build spezification of each project at the same time. Resizeable would be also nice.
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)
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!
how about a "Delete all But this" (similar to Notepad ++) for cases in an case structure. This would save the case-structure and the code inside for the selected case.
I know, that I could delete the structure, keep the active case and get a new case structure around that piece of code...but that's not comfortable.
Say I've dropped two 2D array controls on my block diagram, and would like to change both of their appearances in the same way. I can select each one at a time, right click and head to Visible Items > Index Display. However, it would be nice to be able to select multiple items of the same type and have the option of applying the same change to all of them.
Currently, selecting both and right clicking lets me change the following:
It would be nice if LV could recognise that I've selected two identical controls and offer me the option of changing the display settings for each of them:
Expanding this, you could use the same approach for BD constants, such as setting multiple string constants to '\' code display, or disabling size to text.
As in the subject.
Now when you create an array the indexes of the array can be only labeled as the static comment field. There is not any build-in label/handler which could be used. Current situation looks like that:
It would be better for readibility if developers could name the indexes and use it later on.
Picture represents the idea only, whole point is the description shoud be a build in handlers.
Now LV names first four indexes (when you hover over on it) as column, row, page, vol; later on are only dim 5, dim 6 and so on.
I believe if would increase readibility and save coding and debugging time.
We need the additional properties of the used LabView Editor:
bitness: 32 or 64 bit
ServicePack Number: 1,2,3 ....
Patch Version: f1,f2,f3 .......
So, what i like to have is, that i can get the above listed properties from the currently running LabView Editor, programmatically!
See also forum discussion for the problem:
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?
When entering debug mode (turn execution highlight on) it can be hard to see what is happening.
With event structures it can be hard, but there are subtile changes. Sometimes it's impossible. For instance, if you run this VI, and wait a while, it is impossible to why the VI has not stopped. In this case it's easy to deduce, but it can be really hard. Probes also don't provide a solution here...
SubVI's get a green arrow when they are executing. So, could structures get them as well?
I was searching for occurences of a reference to a Graph in one VI, and as I was interrupted, came back to the search result after the interruption, only to discover that the Search Result Window did actually not show ANY kind of useful information regarding the object I was searching references for:
I know I have outrageous expectations as a LabVIEW user, but this seems to me an odd lack of feature:
- From this window, I have absolutely no clue what I am searching for. In particular, if I have in the mean time jumped from windows to windows...
- ...there is no way to go back to the object these references are linked to (unless I go to one of the references and then look for the Control or Indicator they are associated with).
Of course asking for a VI information when this is provided in the list below is maybe unnecessary.
But consider this global variable whose references I was looking for:
Same thing here:
- I do not know the type of the global.
- I do not know which VI it is part of (Globals are saved in a VI).
- I do not know where I started my seach from (but that's more of a back-to-source button issue).
Suggestion: provide as much information as possible about the starting point of the search, when said starting point is an object (by contrast to a text search).
Tested in LV 2013 SP1 64 bits.