LabVIEW Idea Exchange

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

When compiling a Polymorphic VI with many members, it's kind of awkward to press the "Edit Name" button each time, fill in the values, click OK, select the next member, repeat & rinse.

 

Why not allow direct text entry into the table shown in the picture instead of having to jump trough some loops?

 

Direct Polymorphic VI Menu entry.PNG 

 

Shane.

facf.jpg

 A picture is worth a thousand words.

This new button should finish the actual VI and close it instantly.

When using the LabVIEW Internet Toolkit FTP library to transfer large files, there is no way to determine the progress.

 

I propose a notifier be added to the FTP Registry object data. This notifier would be updated by the low level TCP Read Stream and TCP Write Stream vis and monitored by a UI to display progress of the transfer.

 

See this NI Forum post...

 

FTP transfer progress bar

http://forums.ni.com/ni/board/message?board.id=170&message.id=470946 

 

 

 

 

In LabVIEW 2009, the programmatic API for shared variables and I/O variables was introduced. This allows you to reference a variable by name, rather than dropping a static node on the diagram.

 

Some of the benefits are: iterating over many variables with looping structures, creating modular code, and dynamically accessing variables based on names in a config file for example. 

 

Programmatic access to single-process shared variables would also be useful.

 

(Single-process variables are effectively global variables (not network published), but use the same static node as the shared variable and are contained in project libraries.) 

 

The problem: Free Labels may take too much space on BD to hold all information.

 

Idea 1: Allow Label to have help. With this simple change, the programmer puts the essential information in the label and the details in the help.

 

Idea 2: Create an option to current Free Labels or create a new kind of Free Label, that has a behavior which a hidden part of the information is shown, in a drop-down "flap", when the user hover over the Free Label. The label could have two fields, one for the permanent information always shown (current bahaviour), the other for the additional information that will be shown when the user hover over the Free Label.

 

Free Label with Drop-down additional information.png

 

 

When installing a new version of LabVIEW, I always find myself resetting all of the options I previously changed from the default settings in the Tools -> Options menu. This means I have to spend my time remembering what options I changed and where in the Options menu I need to change them. It would be nice if a newer installation of LabVIEW looked at the older version's Options settings and then applied those settings to the new installation.

 

The same idea applies to how I configure the palettes on the block diagram. It would be nice if newer installations looked at how I configure my palettes and then set them up the same way. 

 

With these changes transitioning to a newer version of LabVIEW might be even more seamless for users that change their settings from the default settings. 

Many users already talked about adding new controls and revamp the current ones. In this topic I will address many issues that I have about the Meter control. Even though I like it a lot, it would be nice if it has more flexibility to customize. Here some ideas:

 

1) Color ramp issues:

  •  
    • Is asymmetric: there is a hidden color in the right most side, that can be only be seen when you change what you think is the last color (red). With the “Interpolate color” option off it is very hard to see and change it;

    • Has a limited fixed number of color steps to customize the ramp looks;

    • Cannot be customized in properties window;

    • Strange correlation between the modes on and off of the “Interpolate color” option:

 

Meter control colors.png


 

  •  
    • Enabling an option, the ramp could appear progressively follow the needle:

 

Meter control progressive ramp.png

 

 

2) When resizing, it would be nice to be possible to change the control's aspect ratio making all internal elements proportionally follow the change.

 

 

3) The user could have an option to rotate it in 90 degrees steps, allowing four positions: normal (0 degrees), right (90 degrees), upside down (180 degrees), left (270 degrees):

 

Meter control 90 degrees.png

 

(The numbers on the scale should be rotated and appropriate 3D shadows should be applied)

 

4) The needle course could have a parameter to determine the curvature. A positive number will give the current aspect, let's say convex. Zero will make the needle become a slider. The nice thing of this is that you can start with something looking as a Gauge (very convex), passing to a Meter (slightly convex), to end with a Slider (strait). I doubt that a concave look, with the needle pointing to the center will be useful because the idea is to make the reading as much clear as possible.

 

I'm Sorry I didn't made pictures to illustrate this case because I have no enough skills do it. I tried to be as clear as possible in the text. If anybody needs any additional information, please let me know.

 Since there is a lot of space we can have a save button which will save a click to save the vis. Another addition is to greyout the button when the save is done or an action is reverted back.

 

 

 With save button

disabledsave.PNG

 

 

 

With save button disabled.

disabledsave.PNG

 It is a very common / preferred practice to design Vis along a horizontal structure of error clusters wires.

 

Sometimes, cleanup does not create a horizontal error wire.

 

Please add a  "force error wire horizontal" option.

 

Thanks

 

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

 

 

We have a Round towards -Infinity  (3.8 becomes 3,  -3.8 becomes -4)

We have a Round towards +Infinity (3.2 becomes 4, -3.2 becomes 3)

We have a Round to Nearest (Rounds up or down to nearest integer, if 0.5, banker's rounding to even integer)

 

Why is there no Round towards Zero?  Basically a truncate.  (3.2 becomes 3, -3.2 becomes -3)

I have a use for that right now, but it takes several primitives to work. 

 

As a corollary, a Round Away from Zero.  (3.2 becomes 4, -3.2 becomes -4)

 

 

Message Edited by Ravens Fan on 01-19-2010 04:53 PM

Building on the "Path Case Selection" idea, it can be difficult to remember all of the values of an Enum when defining a case structure.  I suggest a popup menu on the case structure which lists available values for selection.  Values already defined in other cases could be greyed out, and values selected in the current case could be selectable for removing.  Perhaps it would require a heading to differentiate from selecting a case, and Ctrl-click (Ctrl-right-click?) to activate.

Case Popup

This idea simply extends "Allow References to be wired into Case Selectors" by JackDunaway.  In short, allow paths to be wired directly into a case selector, with one case for "Not a Path", one for "Empty Path", and a third for "Valid Path".  This would often save me small trees of nested cases.

When you’re making a By Reference LabVIEW Object using a Data Value References (DVRs) the user of your class would need to embed each Dynamic Dispatching VI inside an In Place Element Structure (IPE). Or you have to create wrapper VI for each method but this undermines the advantages of LVOOP Inheritance.
 
The idea is that a DVR containing a LabVIEW Object wired to a Dynamic Dispatching Terminal is equal to calling the Method VI inside the IPE structure like illustrated below.

DVR DynamicDispatch.PNG

Message Edited by Support on 01-15-2010 04:39 PM

Since the commands "Group" and "Ungroup" objects it is only available in the FP's toolbar, there is no way to customize a shortcut key to it. The proposed ideas are:

  1. Have the controls also available in the "Edit" menu to allow us the customization through Tools -> Options... -> Menu Shortcuts.
  2. NI define two keyboard shortcuts, for example, Ctrl+G to group and Ctrl+Shift+G to ungroup.

Sometimes, like in many other software that have a paint feature, we need color swapping between foreground and background. The idea is to add a spot in the Tools Palette to allow this operation in one click. Here is a suggestion:

 

swap colors.png

 

It's difficult to see the spot because I did not changed anything, just added the double ended arrow. One way to help the visibility is turn it white when the mouse hover over it.

The tiny circles that represents inversion of the operation in the compound arithmetic node are hard to see (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Enlarge-the-Invert-Circles/idi-p/1023748#A3241). The proposal is to get rid of the circles and invert the central part of the respectives connectors:

 

2010-01-13 compound arithmetic inversion suggestions.png

The difference between the suggestions is that in the second the corners were rounded to reduce the impact a little. I liked the first most.

For non-integer increments, the data entry currently accumulates binary errrors due to the limits if the DBL representation, so e.g. sometimes the upper limit cannot  be reached using the increment button several times, but only when entering the upper limit directly.

 

This comes up at regular intervals, e.g. here. In one fo these discussions, I long ago suggested to make it into an idea. It seems this has not happened, so here it is! 🙂

 

This limitation needs to be handled with some internal code, e.g. to coerce the value to the nearest decimal fraction based on the least significant digit of the increment value whenever the up/down buttons are used. ... or something similar. 😉

I'm sometimes amazed how lazy I get. As soon as a cool new feature comes out, like a For Loop with Break, I want something better. I'm tired of writing code to search through an array of clusters for some specific value that matches. I really want LabVIEW to do this for me. This could drastically improve coding efficiency in advanced applications.

 

Imagine we have a new primitive search function that can search an array of clusters for a specific item and return the index of the first match. Then instead of writing this code manually, I could just drop the function and select the type to search by.

 

This:

 cluster_search.PNG

 

becomes this:

new_cluster_search.PNG

A minor niggle I have is the way LV reacts when we resize windows.  The anchor point is always at the top-left of the window.

 

If I grab the top of a window and make it smaller, I don't get rid of space at the top of the window as expected but rather at the bottom.  This makes alighning the top of the window a painstaking process of resize, adjust, chack, resize, adjust, check.....  I'd live for LV to anchor at the opposite side of wwhere I'm resizing.  If I want to resize the panel shown below to get rid of the space at the top of the panel I insitinctively grab the upper windo edge and resize.  But alas, the result is not what I expect (Even after 10 years of LV programming). 

 

Panel resize top.PNG I want to get rid of the space at the top.....

 

Panel resize top_2.PNGDoh!  Grabbing the top edge doesn't do what I want!

 

Shane.

Message Edited by Intaris on 01-11-2010 09:40 AM