NI Home > Community > NI Discussion Forums

LabVIEW Idea Exchange

Showing results for 
Search instead for 
Do you mean 
Announcements
We've turned on a search before post feature in the LabVIEW Idea Exchange. This new feature will help cut down on the number of duplicate ideas in this space!

The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!
New Idea

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.

 

Untitled.png

JB

Polymorphic VI Selector should snap to VI icon when dragging

Status: New
by Trusted Enthusiast ‎08-28-2014 07:05 AM - edited ‎08-28-2014 07:07 AM

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.

 

Snap to.jpg

 

 

PS : Many thanks to Intaris and TiTou for their help to formulate this idea.

dthor

Copy and Paste VI Properties from One VI to Another

Status: New
by Active Participant dthor on ‎09-18-2014 05:51 PM

I misunderstood ouadji's post here, but I liked my interpretation of it. I didn't find it on the Exchange so...

 

Idea:

Make it possible to copy the VI properties from one VI to another.

 

Method:

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:

CopyColumnProperties.png   PasteColumnProperties.png

 

 

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...):

Revision History

Window Title

 

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 ;-)

oz

 

Hey,

 

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.

AllBut.png

Regards,

CMW..

Xite

Property to get LabView Editor bitness 32bit / 64bit and patch level

Status: New
by Member Xite on ‎09-04-2014 03:17 AM - last edited on ‎09-09-2014 11:41 AM by Trusted Enthusiast

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 .......

 

fixedimage.png

 

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:

programmatically get Labview Editor bit Version

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:

 

select-similar-items.png

 

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:

 

select-similar-items2.png

 

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.

MimiKLM

Allow to name array indexes

Status: New
by Active Participant MimiKLM on ‎09-01-2014 05:56 AM

Hi,

 

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:

 

qwerty.PNG

It would be better for readibility if developers could name the indexes and use it later on.

 

qwertyu.PNG

 

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.

 

cwkao

LabVIEW different version show on the icon

Status: New
by Member cwkao on ‎09-18-2014 12:42 AM

May be the different version can show on the icon.

:smileywink:

LV Icon change.jpg

 

okubik

Create cluster out of selection

Status: New
by Member okubik ‎05-15-2014 04:57 AM - edited ‎05-15-2014 04:58 AM

Hi guys,

I'm missing some very fast way how to create cluster out of selection. It could be done as it is shown here:

 

create cluster.png

 

I think since LV developers became familiar with Every GUI Programmer's Dream they are ready for the next step...

James_McN

Launch Unit Test from Results Window

Status: New
by Active Participant James_McN on ‎09-15-2014 11:53 AM

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.

 

double_click_unit_test.png

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:

 

Screen Shot 2014-08-19 at 18.03.18.png

 

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:

 

Screen Shot 2014-08-20 at 10.12.34.png

 

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.

wiebe@CARYA

Active Structure Debug Indication

Status: New
by Active Participant wiebe@CARYA on ‎06-17-2014 10:13 AM

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...

Parallel Loops.png

 

SubVI's get a green arrow when they are executing. So, could structures get them as well?

 

Parallel Loops proposal.png

SteenSchmidt

Easy toggle tunnel mode

Status: New
by Active Participant SteenSchmidt ‎07-16-2014 08:02 AM - edited ‎07-16-2014 08:03 AM

Hi,

 

After we have gotten several different new tunnel modes, it takes quite a lot of context menu exercise to change tunnel mode on structures:

 

Tunnel_Context_Menu.png

 

I propose a shortcut where we can click directly on the tunnel to toggle between valid modes:

 

Tunnel_Easy_Mode_Toggle.png

 

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?

 

Cheers,

Steen

RENN

Better LabVIEW Help: use F1 to go to the topic

Status: New
by Member RENN on ‎07-09-2014 03:33 AM

helpF1.png

 

 

instead of using the right-click context menu / using ctrl+H and then selecting help,

use F1 to go to the topic

 

 

Latest LabVIEW Idea Exchange Blog Posts
About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
User Kudos Count
84
46
43
37
33
Idea Statuses