LabVIEW Idea Exchange

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

I think that the Abort button glyph should be changed. I see a lot of new LabVIEW programmers use the Abort button as a Stop button. Aborting normally works fine for very small applications or architectures that you learn in LabVIEW Core 1 but not for anything after that. Aborting a VI can leave things in states that you don't want to be in or references open. Sometimes you do need to Abort the code though (other programming environments use Abort buttons) so I don't think we can get rid of it entirely or should we.

 

I propose a compromise of changing the glyph on the Abort button to something other than a Stop sign. I think that some people associate it in the beginning of learning LabVIEW with properly stopping their running code. Unless they learn differently then they will continue to use the Abort button to stop their code. What the glyph could change to is entirely open for debate but I think that something other than a Stop sign might inform users that this isn't the proper way to be stopping code could help.

 

Here's my idea for the glyph but I know there's something better out there:

 

8-12-2011 11-45-23 AM.png

When a VI is saved for a previous version that would result in broken code LabVIEW should warn of this. I thought it did but apparently not.

One of the biggest barriers to entry for LabVIEW and largest negative criticism for LabVIEW is its price.

 

The idea presented here is to reduce the price of LabVIEW Professional from $4299 to $1500. The motivation for this is to increase the LabVIEW community to achieve “critical mass”. That is, have sufficient users that there is a large community offering advice, offering support, writing books, writing handy utilities and generally using LabVIEW.

 

LabVIEW is a great development environment. It can do so much, but its uptake is much less than it’s potential. On the TIOBE Index (http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html), which measures the popularity of programming languages, LabVIEW is not in the Top 50. It could be!

 

Let’s examine the effect of such a change:

 

1) National Instruments profits: We, just like NI itself, would like NI to be successful and profitable. If the price was dropped to one third, I suspect the number of LabVIEW licenses sold would triple. So there (hopefully) should be no negative effect on profit. Hopefully, sales would increase by more than 3 times. There is the issue of support costs, however with some extra effort on addressing LabVIEW stability issues and some more tutorials, examples and broadcast information, the support issue could be addressed. (And the larger user community, which are already very helpful, would be more helpful). With cheaper LabVIEW, NI should sell more hardware, which wouln't hurt profits.

 

2) Existing Users. With more LabVIEW programmers, there would be more community support. With more LABVIEW use in industry, there would be more job opportunities.

 

3) Potential Users: The barrier to entry would be reduced and more potential users would become LabVIEW programmers. LabVIEW should also find more use with hobbyists.

Idea is while loops with time out condition. That means if the maximum duration is exceeded, loop stops executing the code inside and gives a time out error. So we don't have to check the maximum iteration number or time passed inside the code and it prevents unexpected long execution timing.

Timed Out Loop.jpg

 

 

I'm sure we've all been there - with so many toolkits and palettes available for LabVIEW (and sometimes many VI's/Functions within them) it's very easy to end up with a functions palette that's taller than your screen. So LabVIEW adds a scrollbar - it is not possible, however, for you to scroll through the palette using the scroll wheel on the mouse.

 

The current situation:

Using the mouse scroll-wheel will only scroll the front panel or block diagram - you cannot scroll through the functions palette using the mouse scrollwheel. I have tried this in LabVIEW 8.6, 2009 and 2010 and it has not yet been added.

 

NI_Suggestion.PNG

 

The proposed solution:

If the mouse cursor is over the functions palette and it has a scrollbar - scroll through the palette instead of the block diagram/front panel.

 

Why?

Because it'll make navigating through large palettes with lots of functions or large numbers of palettes easier. It is also a natural habit of anyone seeing a scrollbar to use the mousewheel to scroll through the items.

 

I'd really like the ability to write some metadata information in the PNG Write (and read from Read) VIs. JPG, BMP would be nice for completeness.

 

Lately I'm using PNGs a lot. The W3.org spec and most PNG readers allow the use of the "tEXt" chuck tag to allow labels for simple text, keywords include: Title, Author, Description, Copyright,... -- simple stuff.

 

I'd modify the built-in "Write PNG File.vi" but it is password protected 😞

 

My workaround is to write the PNG normally, then tweak the binary file, inserting the tEXt chuck myself, just before the IEND tag, with size and CRC-32 considered.

 

I would really like to see it built in. Perhaps a cluster input with some of the reserved keywords. It seems functionally like a simple concatenation on the file IO stream prior to IEND and file close.

 

Here's the W3 spec for PNG

W3 PNG Specification

 

Thanks!

 

I don't think it makes sense that you should have to switch to the front panel to drop a waveform chart or graph on the block diagram. I believe you should have the ability to create them as you would an indicator using the right click BD functionality.
21057iDC54FE90D1C0289E

I think it would be cool to be able to define custom units in the build unit string function.  For example (%, dB, or Dan's).  The ability to include custom units would remove the burden to include every unit in this dialog.  Adding custom units would also help people who have large complex calculations.

 

Unit Dialog.png

I'd like to see a function that provides default data for any given data type. I think there could be multiple uses for this; I've detailed mine below.

 

In this example, I have a test results array that is indexed by test number. If I run tests out of order, I want be able to fill in the results of the array at the desired index. To do this, I have to add empty rows to the results array up to the current test's index. To do get the default data I used a diagram disable structrue with an empty "Enabled" case, with the output set to "Use Default if unwired. This is obviously a kludge.

 

default_data_disable_struct.PNG

I'd like to see a function that takes in any data type and returns the default data for that type:

default_data_function.PNG

 

 

Message Edited by RandyP on 03-02-2010 11:42 AM
Message Edited by RandyP on 03-02-2010 11:45 AM

The ability to specify a Format String for each index in the Array to Spreadsheet String would let individually saved data columns have different numbers of digits of precision or significant digits.

I use the Array to Spreadsheet String to save 2D column data consisting of Time (X) and one or more Data (Y) columns.  Sometimes the columns have different inherent resolutions yet the Format String needs to be set to allow the largest number of digits for all columns.  This can result in :

0.0000000 -0.0000003
0.2500000 -0.0000035
0.5000000 -0.0000030
0.7500000 -0.0000020
1.0000000 -0.0000013

 

If a different Format String could be used for each index, then the result would be :

0.00 -0.0000003
0.25 -0.0000035
0.50 -0.0000030
0.75 -0.0000020
1.00 -0.0000013

 

If nothing else, it saves on file size.  The Array to Spreadsheet String function could check whether an array of Format Strings was wired into it or not to decide what to do (make it polymorphic).  Thus existing code could still be used.

 

I never really understood why the default count value for Read From Binary File was 1.  95 times out of 100 I am reading the whole file (-1), the other times I am reading a fixed chunk size which is certainly not equal to 1 (and in this case I expect to wire a value).  The 'default' or natural behavior is really to read one byte/word/long at a time?  That is about as inefficient as it gets.
We have multiple developers working the same project. We all store our copy of the source code in different directories. When using Application Builder in the Project, you need to set an absolute path for the build destination. It would be great if this directory could be a relative path from the project file.

The Probe Watch Window is a great addition to LabVIEW 2009 and I like that I have one centralized location to control all my probes.

 

What I don't like is that every newly created probe is embedded in the Probe Watch Window. There are various use cases where this is not desirable (see this discussion on LAVA for more info about it).

 

In the situation where you need the probe to be floating; instead of doing the following (for creating a new probe):

 

  • Right click on wire >> Probe (Or custom Probe)


You have to do the following (for every single new probe):

 

  •  Right click on wire >> Probe (Or custom Probe)
  •  Go to the Probe Watch Window and either:
    •  Click the "Open in New Window" Button
    •  Right Click "Open Window" Button

 

Basically this take twice as much effort as before.

 

I think that we need an ini setting (or a button in the probe watch window) to automatically float probes upon creation.

Tabbing will work for clusters on the front panel, currently we are using "Ctl+Down arrow key" to focus control in the cluster "Ctl+Up Arrow Key" to come out from the cluster

 

For use Tabbing feature for clusters, I need to use "Ctl+Down arrow key"/"Ctl+Up Arrow Key".

 

While tabbing on the front panel is there any way LabVIEW automatically detects the Clusters and it will directly focus the first element of the cluster and when you click Tab on last element in the cluster it will come out and focus the next availble control outside the Cluster (if next control is again Cluster it will focus the first element of the next cluster)

Add the possibility to enable or disable the indexing for a string at the entry of any loop.

The result would be only one char by one char, and would be really usefull !

 

Of course, the same possibility at the exit would create ("build") the string from a char or a string...

String in Char.PNG

Clusters can be added together using the "Add" primitive:

_carl_0-1674589830749.png

Why not support adding them together in the same way using "Add Array Elements"?

_carl_1-1674589902284.png

Hi,

Following this forum thread, I post here my idea:

https://forums.ni.com/t5/LabVIEW/Modern-embedded-web-browser/m-p/4209271?profile.language=fr#M1219530

 

Is it possible to update the embedded web browser in order to comply with HTML5 ?

 

We uses external web pages to improve the user experience in out LabVIEW applications.

 

Regards,

 

Amaury

Wouldn't it be nice if Probes window had a drag'n'drop reorder functionality, maybe even a Sort?

 

Often you (I) place a couple of probes, maybe add some in another VI and then go back and add one earlier in a block diagram. 

Is this a problem? Well, it's not breaking, but i'd like probe 1 to be the earliest executed probe and so on. Often execution order can easily be something like 13, 19, 3 and drag'n'drop #3 below the #19 would the shift them as 3, 13, 19. (Similar to how Reorder Case works)

 

It'd be nice if you could drag this probe in the probe window and it'd change numbers accordingly (switch/reorder within the VI).

Maybe even have Sort button that simply renumbers all as they're shown in the probe window.

 

 

It's somewhat similar, but different, to Altenbachs switcheroo idea: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Probe-switcheroo/idi-p/3126138

When you get an error from an invoke node or property node, the error message sometimes tells you which node generated the error.  But it often does not.  It'd be nice if these error messages always provided you with this info:

 

_carl_1-1635891908407.png

I've spent plenty of time in the past trying to track down the exact node throwing an error, this simple change would've saved me quite a bit of headache.

I searched but didn't see this idea yet. I'm surprised it hasn't already been suggested.

 

The idea is to add a "Build Set" to the Tunnel Mode menu:

 

BertMcMahan_0-1628094318032.png

 

 

Right now we have to build an array in the loop, then convert it with another loop. A native menu option, with the ability to keep the Conditional checkbox, would be very useful.

 

(Similar thread: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-native-functions-to-convert-between-1D-Arrays-and-Sets/idi-p/4019595)