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 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 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 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!
Here we consider a global cluster (first use case) or a function that outputs a cluster and is viewed as icon (second use case).
NOW : GLOBAL VARIABLES POINTING AT TOP LEVEL GLOBAL CONTROLS ONLY
In order to access one item within this global cluster, I have to put on my diagram a global variable pointing to the cluster, and use the "unbundle" function to extract the desired element. Right clicking on the global variable only allows to browse top level controls contained in the global VI (can not directly point at cluster components).
BETTER : GLOBAL VARIABLES THAT CAN IMPLICITELY UNBUNDLE ANY GIVEN GLOBAL CLUSTER COMPONENT
First you would put on your diagram the global variable, pointing to the cluster. Then right click on it and choose in a tree-form menu (alike the menu to choose among properties/methods of an object) that allows to select not only top level controls, but also controls contained within clusters. The global variable would then point directly at the cluster compponent with a name like "Cluster.Component".
Using unbundle function is cumbersome and can be nicely avoided in this situation.
OTHER USE CASE : ICON VIEW VI THAT CAN IMPLICITELY UNBUNDLE ANY GIVEN OUTPUT CLUSTER COMPONENT
For VIs that output clusters (e.g. when the number of outputs is big), the same trick could make it easier to reach specific output cluster contents without the need for an unbundle_by_name operation, at least when the function is viewed as icon.
Sorry, not time for artist views ;-)
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.
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:
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.
Naturally, the first thing you want to do when a unit fails is go to the test definition to understand why it has failed.
I propose that you should be able to double-click the test name or even better the failed test case to launch the .lvtest definition directly from the results window.
When defining a test case in a unit test you often need to import the connector pane or import control values.
This can take several seconds but there is no sort of indication of when the operation is running or complete. It would be good to at least have a busy icon for the duration if not some sort of progress bar.
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.
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?
After we have gotten several different new tunnel modes, it takes quite a lot of context menu exercise to change tunnel mode on structures:
I propose a shortcut where we can click directly on the tunnel to toggle between valid modes:
I say valid modes as not all modes are valid for all tunnel data types, for instance the "Concatenating" mode isn't allowed for scalars, but is still selectable in the context menu resulting in a broken scalar wire leading to the concatenating tunnel - the toggle should perhaps skip such an invalid setting? Or maybe not, in case you're preparing to change data type and just want to toggle the tunnel first, I don't know.
Tunnels on different structures have different modes. On case and event structures the modes you could toggle between would be 'Use Default If Unwired' on/off for instance.
Am I the only one feeling there's a long way into the tunnel mode menu now?