LabVIEW Idea Exchange

Community Browser
Top Authors
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Another request from my carpal tunnels here.  When you Right-Click and Create Indicator, you get the indicator wired to the terminal you selected.  When I right-click a reference and Create Property For... or Create Method For... I would like to get the PN/IN wired to the reference.  Right now it gets placed on the cursor when you select the property or method, and if you are unlucky, that can be a considerable distance from the terminal.  Now you have to drag it back into position, hope for autowiring to catch, or wire it up yourself.  I would much rather have it placed and wired automatically.

 

CreatePropertyForFromReference.PNG

The pane properties dialog is rather limited:

24116i402FDA4F25C800F2

 

It only shows 4 options:

-Label

-Label Visibility

-Background

-Background alignment

 

It could also show the following dialog:

So it adds the following properties:

-Origin

-Scroll bar visibility

-Minimum pane size

 

Currently you have to create some special code to set these options.

 

Ton

 

I have just noticed a difference of 2 pixels in the width of the input fields of the Label and Caption.

 

Spoiler
Although they don't look like, in below example, the label and caption are the same.

 

Label_Caption Width.jpg

By default, when you build an application, the front panels of all VIs are removed.

 

Of course, this would make applications completely unusable, so there are certain changes which cause LV to keep the front panel in, such as setting the front panel to open when the VI is called. This gives LV a clear indication you want the front panel and these changes are generally enough for most of the VIs which people use.

 

There are, however, times when you want a VI to keep the panel, but it's a VI which usually (or sometimes even never) won't be displayed. Today there are several ways to handle this case.

 

 

The official way is too flimsy:

 

Keep_FP_AB.png

 

 

It's limited to specific build specs and it's too easy to break (e.g. remove the VI from the project and add it back).

 

 

 

 

The automatic way relies on additional changes you're likely to make if you intend to show the VI, but is also too easy to break:

 

Keep_FP_Property.png

 

Someone could just unset the property and then it's gone.

 

 

 

 

What I usually today is something like this:

 

Keep_FP.png

 

The static property node ensures the FP will remain and the comment makes it less likely that someone will remove it.

 

 

 

 

What I want to see, however, is something more explicit, possibly in the shape of a new VI property:

 

Keep_FP_New_Property.png

Hi,

So in VI Properties, you have the Window Appearence tab with "Same as VI name" tickbox.

Wouldn't it be great/better if this automatic name skipped the file extension?

 

Settings.vi -> Settings

OneButtonDialog.vi -> OneButtonDialog

and so on.

 

/Y

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!

 

 

 

When you move files around in the directroy structure (not renamed), you get prompted with this Resolve Load Conflicts message box.

For every VI file used something that has moved you must choose if you want to:

 

a) load with the file found in the new location.

b) load the file that can no longer be found.

 

I proposed having a way to automatically load the newly located file with the alternative cannot be found

OR

having a "Resolve All Conflicts" button for this case.

 

 ResolveConflicts.jpg

 

ResolveConflicts2.jpg

 

 

Dear All,

I wish adding Last modified date and time in Getting Started window  in recent list will be helpful for the developer.

 

Project Files.png

It could be useful to have the possibility to set the Runtime Menu of a control by specify the .rtm file

 

RuntimeMenuPathForControlClass.png

Dany

We currently have an API to edit it

 

MenuAPI.png  

 

What I propose is to extend it with a couple of new function:

 

Open/Create Menu File : Open/Create Menu File return reference to the menu.

Open_Create_Menu.png

 

Write Menu File: From a reference save the file to disk

WriteMenu.png

 

Close Menu File: Close the reference to the menu file

CloseMenu.png 

 

Dany

I would like to propose the use of a stacked parallel execution structure.  Especially in FPGA applications, this will solve the problem of diagrams running off the screen.  All execution pages will run simultaneously as if independent while loops were scattered across the BD.  This idea potentially leads into a 3 dimensional visuallization of coding LabVIEW. Note: In the image, the pages are offset but should look similar to a stacked sequence structure.

 

 

Parallel Execution Structure 3.JPG

 

 

untitled.PNG

 

OK, so what happens to the index displays if you click the top buttons, the ones with the arrows pointing up?

Spoiler
the Ring and enum indicies DECREMENT

 

I would propose to make the behavior consitant so that UP increments and DOWN decrements

So, i just found a bit of code with a parallell loop, containing a non reentrant vi, making it moot. I guess we've all been there, and those things can be hard to spot.

 

Suggestion: Mark reentrancy with an automatic small corner icon similar type def, e.g. in different colors depending on if it's Shared or preallocated.

Reentrancy.png

LabVIEW should expose a method that allows you to "drop-down" a combo box programmatically.

 

Something similar to the issue discussed in this KB article:  http://digital.ni.com/public.nsf/allkb/96BD56FE6D416AB5862573BE00811AC2

 

A simple invoke node would be great.

This is somewhat related to this idea by GregS, but still not quite the same.

 

The array index terminal of an In Place Element structure currenty require to be wired. It should exactly like "index array" such that unwired inputs behave like the plain old Index Array (an unwired index is the index of the above terminal +1 (recursively). The top terminal defaults to zero).

 

As an example, here's a simple construct that keeps the N, average, min, and max in a size 4 array. For some reason, the code is broken unless I wire indices 0..3. None of the indices should be necessary and the functionality should remain exactly he same without them.

Message Edited by altenbach on 12-28-2009 09:58 AM

Hi,

 

wouldn't it be nice to set the access scope for multiple VIs in the project tree? Currently you have the possibility for using virtual folders. When I right-click on multiple VIs i can analyze them, run unit test, etc. Currently we're building the hierarchy of virtual folders according to functionality and not by access scope.

 

I searched the ideas but didn't found such an idea. If so, please don't shoot me for a double post.

 

Right Click on Multiple VIs

Like some other ideas here and here, I find the connector pane right-click context menu to be a burden. I would like to see some of the menu items moved or rearranged.

 

For example, I’ve been using LabVIEW a few years, but the first time I tried many of the shortcut menu items was today. If I were looking for them, I would probably expect to look under "Patterns".

Picture1.png

Additionally, if I click a little to the right, three more of the menu options are already available in a much shorter context menu, so I don't feel like they are needed from the connector pane. (Personally, I rarely perform these actions through the icon, anyway, but I’m sure some people do.)

Picture2.png

 

I propose removing the top few items and putting the others in the patterns sub-menu.

Something like this:

Picture3.png

Picture4.png

Or, if combining the text and patterns creates a UI programming issue, I think it would be acceptable to leave "Patterns" and add a new sub-menu:

Picture5.png

Picture6.png

 

Thank you for considering this idea!

-joeorbob

When using a case structure with many cases I often need to check where a given input is wired (and used).

Maybe It could be useful to have a right-click feature that can allow to jump to the cases where an input is used, as shown in the picture:

 

19085i403F476FB9FE79AF

Element of Set? returns whether a single element is a member of a set. In order to check multiple elements, we currently have to place multiple nodes on the block diagram, which is rather redundant:

 

Current Situation.png

 

I would like to be able to connect multiple elements to a single node and check all elements at once:

 

Desired Behavior.png

 

As an example, I need to check if either of two elements is part of a set. If one of them is, add the other, otherwise do nothing:

 

Example.png

This is certainly not a deal breaker, but in my opinion it makes sense to allow multiple elements to be connected to this node, especially considering that it is read-only.

Store webservice "source code" in a separated file like VI, libraries, classes ... not in project file so a webservice can:

- Be versioned in source code control

- Be reused between targets

- Be reused between projects