You can open a type definition by right-clicking a diagram terminal, constan, or front panel control, but it is not possible to get to a type def file just from a wire. There are a lot of times where I'm working on a diagram that uses a type definition that is only exposed as a wire. Right now, the process of getting to the type def is to create a temporary constant from the wire, then right click the constant. It would be nice to make it easier to get to the type def. And of course, I would like to have the same functionality for LabVIEW classes.
I suggest that radix is always visible when the numeric display format is other than decimal. Is this number decimal for instance?:
Well, it was hex:
... -> ...
Basically you'd know that if there isn't a radix visible, then the number is decimal. It should still be possible to show radix for decimal numbers as well. This should be the case for both constants and controls/indicators.
Just one of those little things that would enforce a minimum of documentation.
If there is a "Move Up" and "Move Down" option is available for "Unbundle by Name" and "Bundle by Name", then it would be very helpful. Then, instead of deleting the removing the items and then inserting the same item in some other row, I will just move it up or down....
Sometimes when dealing with the Bundle/Unbundle by Name nodes, I start with more elements than I actually end up using. Then, my block diagram looks something like the following:
Maybe I'm just lazy, but I really hate removing each unused item from the Bundle/Unbundle by Name node over and over. Right click on unused element, click "Remove Element", Right click on next unused element, click "Remove Element", etc... Ugh!
So I'm suggesting a "Remove Unused Elements" when you right click on a Bundle/Unbundle by Name nodes. With this option, right clicking on one of these nodes would look like this (emphasis added ):
The result of this operation would look something like this:
Now I can spend my time coding instead of getting rid of individual elements! Thoughts?
I don't know how many times I've wanted to add Error in and Error out terminals to a VI retrospectively and have to visit the cluster palette twice to do just that.
How about (for those of us who don't yet use Quickdrop) an option to drop an Error Cluster pair (Both in and out) to save us a trip to the Palette?
That's it really.
when you right click on a color property node, and select create constant, the result is a U32 constant !!!
so that you have to know the representation of your color in U32 formats, or you will replace it with a color constant.
I think it will be nice when I create a color constant to create a color constant not a U32 constant.
I work with customers who use multiple versions of LabVIEW. Being able to run two (or more) different versions of LabVIEW concurrently is a boon to my development and productivity. However, identifying which version I am looking at or have open can be difficult.
Can YOU tell which versions I have on the taskbar?
To remedy this, I suggest a version badge be added to the taskbar icon for LabVIEW. This will facilitate quick identification of LabVIEW versions.
Ohhh, its LabVIEW 2011 SP1 and LabVIEW 2012!
I suggest having a feature that would allow us to add "virtual" error terminals to any VI by right-clicking any VI and selecting "Add Virtual Error Terminals...". These virtual terminals would do nothing more than act as pass-through tunnels to facilitate data flow. This would allow us to minimize the use of sequence structures:
Sometimes I want to insert a unconnected Sub VI on my panel into a some wire. I always end up deleting and reconnecting the wires to insert my Sub VI.
I miss a solution to quick insert a VI into a wire without deleting and reconnecting the wires.
I know we already have the option to use the QuickDrop with ctrl+I, but I miss a solution to insert a VI (that already exists on my panel) into a existing wire.
What about clicking on the wire and draging the Sub VI while pressing crtl+i?
I sometimes need to create Front Panels that are to be navigated by keyboard alone, which makes the tabbing order quite important. At this stage, I need to ensure my error cluster controls don't get included in the tabbing order list. Given my error cluster controls for any VI that shows its front panel will be moved out of the visible area, I need to ensure the operator cannot tab to them. Therefore, I would like to see error in clusters have their default "Skip this control when tabbing?" property set to True.
I don't think a change to the default property would cause any complications?
This idea is a better idea than my previous Error Cluster disabled by default thanks to tst!
I'd really like to be able to select the entire top-level cluster in an event structure, if event data is a cluster:
I know this have been brought up in numerous forums over the years, but I feel it's being ignored somewhat by NI? It usually gathers quite a few positive acknowledgements from other users, but I think it's about three years since it's been brought up in the idea exchange. It seems so easy to implement and would greatly simplify many event structures. So forgive me for duplicating something from countless other places, but I think it deserves a second (or ninth or whatever) glance
In LabVIEW if I want to use a property/method of a control I have to right click and select property. Same for second control I want to use same property I have to do same operation again. My idea is if we select all the controls and right click, some common property like value, visible and etc..... Should display and by selection it generate automatically. This can reduce my application development time.
So if this key feature is there in LabVIEW we can select multiple controls or properties and perform some basic operations to reduce our application development timing.
Thanks and Regards
Himanshu Goyal | LabVIEW Engineer- Power System Automation
Values that steer us ahead: Passion | Innovation | Ambition | Diligence | Teamwork
It Only gets BETTER!!!
I'm not sure if this is a bug report or a feature request, but I think it should be fixed/implemented, all the same
If you right-click on a Boolean funtion (And, Or, Exclusive Or, Not, etc.) and replace with a Compoint Arithmetic (CA) function, the CA function is always set to the "Or" configuration. I would expect it to be smart and put the CA node into a configuration (including negation/inversion dots) that is equivalent to the Boolean function that it replaces.
When you drop a local or global variable, it always defaults to Write. Wouldn't it be nice to drop a variable down, and it is "uninitialized". It would show nodes on both the read (left) and write (right), and become either read/write only AFTER you wire to the appropriate node.
When doing UI work, it can be quite frustrating rewiring hidden controls to the connector pane. You have to go to the block diagram -> Show Control -> go to front panel and wire it up then hide your control again.
I have seen a number of ideas proposing ideas such as hidden controls always being visible in edit mode or being able to link block diagram controls to the connector pane which I agree with and would also solve this.
My suggestion is that when you select the Wiring Tool on the front panel or click on the connector pane (to wire up a terminal) all the hidden controls would become partially visible and become connectable to the connector pane.
Let me quote my old opinion here:
"Which I think should NOT be the default behavior: It "fixes" potentially incorrect code by throwing even more potentially incorrect code at it. I can't remember a single instance where I wanted that behavior."
While I wish this option would disappear completely, I think at least it should be off by default.
There are plenty of examples (e.g. here or here) where an auto feedback node insertion covered up a serious dataflow issue by making the VI no longer broken. This is a disservice to the new programmer who might not even understand what a feedback node really does.
A feedback node needs to be intentionally placed in all cases.