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
SFK

allow blocking of NaN in numeric data entry

Status: New
by Active Participant SFK on ‎10-24-2014 11:12 AM

Recently, I discovered an annoying "feature" of LabVIEW: if you limit the data entry of a floating point numeric to a maximum value with coercion enabled, entering NaN to that numeric will be coerced to the maximum that you set in the data entry dialog.

 

I already reported that as an unexpected behaviour, but after some more thinking, I dare to go even further and propse:

 

allow the blocking of NaN in floating point numeric data entry

 

idea_discard_nan_data_entry.png

 

The logic needed should not be much more than a finger exercise, as string controls already allay to discard CR/LF with the "limit to single line" property.

 

Best regards,

Sebastian

Norbert_B

Probe terminal

Status: New
by Trusted Enthusiast on ‎10-24-2014 06:49 AM

During implementation of code, the algorithm and its implementation has to be tested and debugged in most cases many times. For debugging, probes are a very useful tool. But probes can only be created on existing wires.

If, for any reason, the developer wants to probe values which are not on a wire already (e.g. iterator of a loop), he has to create an indicator (or tunnel) in order to have a wire. Once the debugging is done, the terminal/tunnel and the wire should be deleted.

 

I find it would be much easier, if i could right-click the data output and select Create >> Debug Terminal. This terminal is part of the code, but once i close the probe, the items created by this option (terminal and wire with probe on it) are removed automatically.

 

Norbert

 

PS: I know that there was a suggestion specifically for the iterator of a loop. I understand the reason why it was declined, but i find that using VI Scripting, the above mentioned functionality could be provided. As i WANT to have the information of that wire during debugging, i require that terminal/wire in any case. Using some automated tool would ease the debugging process with the hope to decrease time required to identify the software anomaly.

0 Kudos

Many of the VIs or projects that I create are just a learning experiment to get things in the right direction. My startup screen is overflowing with junk files that I never need to see again. I would like a "right click --> remove item" when you hover over junk files in the right pane of the LabVIEW startup splash screen.

 

LabVIEW splash screen suggestion.JPG 

0 Kudos

Logical shift in LabVIEW discards the shifted out bit. Logical shift functions in assembly labguage settings shift that value to an overflow bit register allowing the bit in question to be tested and program flow to be altered.

 

This kind of function is useful when dealing with low level protocols at the bit level, or dealing with digital devices that have a parallel interface.

 

I suggest the logical shift function have an additional output that contains the boolean value of the bit just shifted out of the number.

 

Logical shift should be able to output a single boolean, or an array of boolean. For the single case, the value would be the last bit shifted out with other bits being lost. For the array output, all bits would be captured with the first bit shifted out being the 0th index of the array.

0 Kudos

I just updated from LabVIEW 2012 to 2014, and somewhere along the way it seems the "Key Navigation" mechanism has changed.

 

When running a VI, sometimes it's very convenient to adjust the value of a control using the keyboard arrows (moving the caret left/right to select a digit and incrementing/decrementing using up/down).  During this, I frequently need to toggle other controls, for which I've configured the "Key Navigation" settings such that I can do so without needing to switch over to the mouse.

 

In 2012, the caret navigation would stay active (i.e. focused/locked) on a given control while I toggled other controls through "Key Navigation".

In 2014, if the caret is active in a numeric control and I toggle another control through "Key Navigation", the focus is lost and I have to use the mouse to place the caret back where it was.

 

I should note that this doesn't seem to happen with the "Increment" or "Decrement" modes of "Key Navigation", just with "Toggle".

 

Not sure why this was changed, but having to switch between the keyboard and mouse frequently slows down workflow considerably.

Status: Declined

This is a bug being tracked as CAR 502190

Here's an idea to make better use of front panel pixels and printer paper.

 

Problems Solved:

1)  Too much data to show on one screen using regular controls, instead of tabs, Show at-a-glace highlightable data in a configurable cluster format.  Before LabVIEW 2014 the typedef table inside a typedef cluster would do thes fairly well.

2) Use same panel as print format since it is at-a-glance and one panel, WYSiWYG printing made easy

3) LabVIEW2014 crashes when table typedef is nested in a cluster typedef - this suggestion is improvement, not just workaround.

 

Suggestion:  Bring back super space efficient (flat plain) controls and indicators, so I don’t need to worry about NI dropping support for the classic plain text one.  This will allow me to make my own table like displays using individual fields in a typdef cluster.  I could just format a big string control and write code to fill it in by row-column position, but that looks so DOS.  How about marketing it as a report builder cluster like panel builders available in many text based languages?

 

Implementation:

1) Add space efficient flat controlls and indicators to current palette, similar to flat string control in classic palette.

2) Allow these to be placed into a flat cluster that can be typedef

3) Provide a fast way to lookup controls contained in this cluster by name, similar to get array of references and loop through for name match.

4) If desired make an Express VI to build a GUI / Report cluster similar to the way text baased programs do it.

5) Provide for setting printable paramters - shape designed for portrait or landscape and with about the right number of pixels so it fits easily into the printer (no extreme zoom in or out to fit, no half of the printed page left blank, etc..), using this shape as a starting point, nice printable panels will be easier to make.

 

Thank You

Robert Thebert

0 Kudos
Yamaeda

Switcheroo on Select

Status: Duplicate
by Trusted Enthusiast on ‎10-20-2014 09:32 AM

(Unless it's been added in newer versions, i mostly work in 2011)

 

Allow Switcheroo on Select terminals, just like on Add, Subtract and others.

Ofcourse the Selector is excempt from the switch, it's just the terminals that should swap.

 

(In case you didn't know, ctrl-click on Add terminals switches their place)

 

/Y

0 Kudos
christian_w

conditional set variable

Status: New
by Active Participant christian_w on ‎10-20-2014 12:44 AM

I'd like to have an optional conditional terminal for global variables (write) instead of using case structures.

conditional.jpg

 

SteenSchmidt

"View As Color Box" option on numerics?

Status: New
by Active Participant SteenSchmidt on ‎10-19-2014 02:00 PM

Hi,

 

There are numerous ideas floating around about where the color box constant and control should be located in the palettes. How about if there wasn't a distinction between a color box and its numeric representation? Like the "View As Icon" option on terminals and clusters, I suggest a "View As Color Box" on numeric constants and controls/indicators:

 

ViewAsColorBox.png 

 

I'm undecided on if this options should be available for all numeric data types, integers only, or U32 only, and what should happen to the Representation options when the numeric is a color box. I see at least these options (ordered after my preference - I prefer 1) the most):

 

1) The "View As Color Box" option is available for all numeric data types, but when selected the data type changes into U32. If you change Representation to anything else but U32, the "View As Color Box" option is automatically deselected.

 

2) The "View As Color Box" option is available only when the numeric is U32.

 

3) The "View As Color Box" option is available for all numeric data types, and coercion happens between the selected "color value" (U32) and the true Representation of the numeric.

 

Several ideas would be fixed by this, for instance this and this.

 

Cheers,

Steen

0 Kudos
xl600

Enhancements to the sampling probe (FPGA)

Status: New
by Member xl600 on ‎10-17-2014 01:36 PM

The sampling probe (FPGA simulation mode) is extremely handy for quick testing of FPGA algorithms.  It's clunky though and needs some enhancements.

 

1.  Align signal names to waveforms under all circumstances.  Currently, the alignment is all over the place, especially when zooming.

2.  Fix the zoom feature!  Currently, the zoom in and out behave in random ways.  Sometimes zooming vertically, sometimes only horizontally.

3.  Merge the zoom in/out buttons into a single "Horizontal zoom" where the shift or ctrl keys alter the in/out.

4.  Add a dedicated vertical zoom button which will also zoom the space between signal names so alignment is assured.

5.  Increase the highlite effect on the selected waveform.  It's hard to see.

6.  Add the ability to save probe configuration so the probe doesn't have to be rebuilt every time.  I've often found myself adding upwards of 20 signals and hate having to re-add those (In the same order) whenever the window gets closed.

roto2

Color box control and color box constant place in tools palette

Status: New
by Member roto2 ‎10-17-2014 02:35 AM - edited ‎10-17-2014 02:42 AM

I'm using 2012 version, so I don't know if it's the same for 2013 and 2014 versions.

 

I don't use color boxes very often but when I do I always have the same problem when looking for them in the tools palette.

 

When in the front panel the Color Box control is situated in the Numeric folder

 

 NI_001.png

 

 

But when in the diagram the Color box constant is a little more hidden...

 

 NI_002.png

 

 

I know there is the "Search" option, which works very well. Also I can choose the color box control in the Front Panel and change it to a constant, but I worked for a lot of years with version 6.0 to 7.1 and it was very intuitive to find the constant where it was, i.e. here:

 

NI_005.png

 

 

So why don't leave the color box constant with the other numeric constants?

 

By the way, thank you for reading, I always wanted to comment this :robothappy:

 

Currently (LV 2013 SP1), this contextual menu option is only available for constants on the BD.

I see the difference between a constant and a terminal: the former doesn't have a counterpart on the FP, hence that is the only place you can perform this action.

 

But consider this: the Indicator is an output variable of the VI and is hidden somewhere in an invisible region of the FP which I don't want to have to scroll to, perform the "Disconnect from Type Def" and then go back and try to recover the initial layout of the FP.

 

Or this: you can use the "Make Type Def." contextual menu on a Control/Indicator terminal on the diagram.

 

Once this consistency issue is resolved, I'd suggest to expand this to local variables of said Control/Indicator, although unfortunately, there is no indication on a local variable that it is a Type Def, as there should.

0 Kudos
jdervin@cox.net

Support JTAG on the 8452

Status: New
by Member jdervin@cox.net on ‎10-16-2014 09:07 AM - last edited on ‎10-16-2014 10:39 AM by Member dcarva

It would be really nice if the 8452 supported JTAG.  With I2C and SPI the only communication protocols that are widely used are RS232 and JTAG.  With the addtion of these one could test the peripherals of most dsp's and embedded controllers as well as create their own programmers and debug tools.

PaulG.

Incremental search

Status: New
by Active Participant PaulG. ‎10-15-2014 02:54 PM - edited ‎10-15-2014 02:55 PM

list.PNG

 

As the number of records gets larger the more difficult it is for an operator to find an exact filename, especially when the first 5-10 characters are the same. I would like to have incremental search, AKA autocomplete, AKA search as you type, AKA filter/find as you type, inline search, instant search, word wheeling ...

 

This works well in windows explorer but I find no native incremental search in LabVIEW.

ghighuphu

remove history for renamed and newly saved files

Status: New
by Active Participant ghighuphu ‎10-15-2014 04:34 AM - edited ‎10-15-2014 04:35 AM

In my settings I have set that some automatic messages appear in the history of VIs (renaming and so). Now, I wanted to save a VI for a previous version of LV (downconvert form LV2014 to LV2010). I deleted the history for the LV2014 file and saved for previous versions. The history of the downconverted VI contains a single line (renaming) with my name in it. Now, I cannot edit and (re)save the file -- either it will be saved in LV2014 or the line will be there. It's a vicious circle. I suggest an option in the saving windows at saving (renaming) any VI: delete history (yes/no).

 

Right, I can unset the option in the Options for the Lv installation and then set them again. It's a workaround, but not a happy solution.

jeff.kittle

propagate lvlib protection to all vi's in lvlib

Status: New
by Member jeff.kittle on ‎10-14-2014 03:12 PM

I would like to see an option added to the Project Library Properties: Protection to propagate the protection setting (and password) to all vi's owned by the library.

 

Currently if you lock a lvlib it only prevents adding or removing vi's from the library.  To lock the vi's from editing you would need to open and change the properties of each vi.

Sometimes you might have a cluster constant, indicator or control on the block diagram or front panel without the labels shown. When you have a large cluster it's not immediately obvious which element you're editing/changing.

 

When you hover over a SubVI, the connector flashes on the Context Help window and eventually a tooltip appears on the block diagram under the mouse cursor as shown below:

2014-10-14_16-25-28.png

 

I propose that, just like when you hover over an input/output of a SubVI it does the same to show the element name on clusters on the front panel / block diagram, as follows:

2014-10-14_16-28-05.png

 

I know it's not the most exciting of suggestions but I think it would be good for usability.

 

tobyscott

Resize Text (Comment or String) with Double Click

Status: New
by Member tobyscott on ‎10-13-2014 07:19 AM

This idea is somewhat similar to Shrink-Wrap-Structures but for comments and strings

 

The idea is to resize a comment or string to the text by double clicking one of the resize indicators around the box.

This would happen without changing the number of lines or words on each line.

resize double click.png

The process would be resize the horizontal direction of the box until the line layout looks nice (and fits!) then double click the corner to remove the unwanted space.

There could be different resize processes depending on the corner or edge you click eg. double clicking bottom middle resizes to only remove vertical space, top left would resize and shift the text down and right so the bottom right corner remains anchored.

 

There are some other ideas about resizing multi line comment boxes but none were quite as straight forward as this so I made a new post for it.

 

This mechanism is similar to other programs for resizing boxes so it seems like a sensible thing to implement.

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
96
65
55
49
36
Idea Statuses