LabVIEW Idea Exchange

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

When concatenating arrays, a wired empty 1D array, concatenated to an Empty 2D array will result in array index (1,0) and when this is concatenated to a populated 2D array, a top row is added with empty elements. This is in many cases unwanted behavior.

 

The suggest that LabVIEW includes a menu to configure the concatenate array node to ignore acting on any empty array(s) wired to that node.

 

Suggested New Menu Item for Concatenate Array.png

 

Because in some cases the resulting array will end up with an added top row with empty elements.

 

2D and 1D Empty Arrays yields Extra dimension.png

 

Anthony Lukindo

When a third party add-on expires you get a dialog asking you to activate it, but the dialog does not offer you the option to remove it instead:

 

Mads_0-1665130603004.png

 

If would be nice to be able to select add-ons in the add-on list and then click a Remove/Uninstall button (and/or right-click). The current solution is to manually fire up the package manager and uninstall it from there (the remove button could alternatively (if needed /quicker to implement) call the package manager and tell it to start the removal of the selected packages.

If you are going to call it a developer suite, put the developer tools in it. The following toolkits need to be added:

 

  • NI LabVIEW VI Analyzer Toolkit
  • NI LabVIEW Desktop Execution Trace Toolkit
  • NI Requirements Gateway
  • NI LabVIEW Unit Test Framework Toolkit

Of course this will increase the cost of the developer suite. I find it easier to convince my boss to approve a cost increase versus purchasing a new toolkit.

Hi,

 

building a large project consisting of several executables and an installer is no problem when using the AppBuilder API.

But a quite time-consuming task is to open all build specifications to update the build path or the file  versions.

E.g. opening the build specification of an installer containing several executables can take up to a minute even on an up-to-date pc.

 

So I suggest to enhance the AppBuilder API with property/method nodes to manipulate the "often-to-be-changed" properties. An example is attached below.

 

Regards,

 

Bastian

 

AdvancedAPI_lvie.png

I need a format into string that is capable to format numeric with thousands separators.

Like this  (Visual Aides - Numeric Separators) idea but also for the conversion and scan functions.

 

Looking at the syntax

 

%[$][-][+][#][^][0][Width][.Precision || _SignificantDigits][{Unit}][<Embedded information>]Conversion Code

 

 

the  <Embedded information>  currently used only for time formats would be ideal to extend to a more general form. 

 

Something like <+ nnn nnn.ddd ddd> would be nice 🙂 ( the d is already occupied ... # or whatever .... maybe similar to the excel format syntax or maybe there is a (better) standard??? )

 

Currently I use the attached vi to add the separators, however it would be nice to have it in a general form 

 

 

 

It's a common convention that the space bar is used to pause/un-pause videos that are playing. It would make sense to me that pressing the space key would toggle the pause button (Pause / Continue).

 

1) Pressing Space Bar key would be the same as pressing "Pause" on the VI toolbar.

 

2018-03-15_10-07-07.png

 

2) Pressing Space Bar key again would "Continue" (un-pause).

 

2018-03-15_10-08-31.png

When you run the LabVIEW Platform DVD, the default setting is that LabVIEW gets installed and nothing else. You can then go pick and choose what modules and toolkits to install. I like this default because I usually only want to install LabVIEW and a few other modules and toolkits. It is faster for me to select the few modules that I want to install rather than unchecking all of the modules I don't want to install.

 

When you run the Device Drivers DVD, it tries to guess what drivers you want installed based on the software you already have installed. However, it usually wants to install more drivers than I want it to install. It is a hassle to go through the driver list and unclick the drivers I don't want to install because most of them have dependencies that you have to unclick first. 

 

Idea: Their should be a button on the Device Drivers installation screen to unselect all of the drivers (see image below). I don't think the Device Drivers DVD default should be the same as the Platform DVD; a lot of new users won't know what drivers they need and installing all of the recommended drivers is a safe bet. However, many users do know what drivers they want and it saves time and hard drive space to only install the necessary drivers. Adding an "uncheck all" button would make this process faster and less frustrating.

 

device drivers.png

Add an "Uncheck All" button!

For LabVIEW users,

How many of them need "Delete Option" on Right Click Context Menu?

Delete option in Context Menu.png

I feel providing an delete option in right clicking context menu for any Indicator or Control deleting will make developers easy and fast assessable and avoid too-much use of keyboard.

We use our left hand for control and Shift more offen but for pressing delete button which is at right top corner in keyboard, all of a sudden we will remove our right hand from mouse and press Del which is uncomfortable.

 

So, Developers share your point of view for the same and request to add Delete Option in upcoming version.

Later we will ask even Cut Copy Past...:smileyhappy: He! He! He!

This is a simple suggestion regarding returning all variant attributes from a variant in the correct data type if the name is left unwired but the default value is wired.

 

As you probably know, if you leave the name and value terminals unwired the "get variant attribute function" will return an array of names and variants for all of the variant attributes. If you wire the name or the default value then the node will adapt and return only a single value with the 'found?' output.

 

Here is a diagram to show you what I'm talking about:

2015-02-18_11-55-39.png

 

Currently, if you leave the name unwired but wire the default value this results in a broken block diagram.

 

The reasons for this suggestion are as follows:

  • Cleaner block diagrams - if you know all of the variant attributes are the same data type then you save the extra constant/variant to data node
  • Possible performance improvements - maybe NI does (or can do) something to improve the performance/memory allocations if the data type is known and can be done within the SubVI
  • I can't see a case where it would break compatibility other than perhaps a broken block diagram would no longer be broken if the default value was wired but not the name but the runtime functionality would remain the same
  • As variant attributes are a very efficient and recommended way of doing key/value lookup tables I think this minor change will tidy things up nicely and if there are performance gains to be had under the hood by doing this then all the more reason to do it!

Thanks for reading and hope you'll +1 my idea!

 

 

LabVIEW has a feature that allow to quickly navigate from one occurence to another in the search result window (see image below).

 

Search Result.png

 

I propose to add the same functionality to the error window (see below).

 

New Error Quick Navigation.png

 

PJM

Message Edited by Support on 06-16-2009 06:25 PM

As seen here, the property pages are sometimes like swiss cheese, i.e. full of holes! Useful and often-used properties are missing, even though they are available via right-click.

 

One example is "Loose Fit". There is no logical explanation why it has been omitted from the scales property page. I suggest to add it!

 

Here's how it could look like:

 

 

 

IDEA: Add "Loose Fit" to the property page.

 

So many times, Darren's history probes have been a great help while debugging my code ! This concept may be enhanced. But at least, these probes should ship with the LabVIEW installer.

Please add the circle constant tau, to the Math & Scientific Constants palette.  Happy Tau day!  (see more at http://tauday.com/)

 

Tau Constant

Many versions ago, we got the "static VI reference", and it made our life easier. I am suggestion a similar "static control reference" that can be tied to e.g. a strict type definition *.ctl file so we can read certain properties.

 

I have several type definitions that are exclusively used as diagram constants. Since there is no control in sight, I cannot use a direct property node. It would be a shame to have to place a hidden instance on the front panel just to get to the properties.

 

Well, we can use a static VI reference to point to the *.ctl file and start peeling until I get to the actual control (top image). However, it would be nicer if the static control reference would directly give us access to the properties of the control, such as the strings of a strictly typed enum in my case here.

 

With my suggestion implemented, the same code could be done as shown (bottom image)

 

The current way to get a static reference to a *.ctl file via a static VI reference (as described above) should be retained, because sometimes we need access to other properties.

 

I am suggesting a new dedicated "static control reference" that would give direct access to the properties of the actual control in the *.ctl file.

 

(of course some properties (e.g. value) would not make a lot of sense if used this way. Maybe there is a much eaier way, but I haven't found it).

 

 

I have an application with multiple Waveform Charts, each with a visible Plot Legend, Scale Legend, and Graph Palette.  I'd like to give each Chart a distinct color (a sea of gray is boring).  There is a Frame Color property that does the Frame, and I figured out how to color "underneath" the X Scale numbers, but I can't programmatically color the Plot Legend, Scale Legend, or Graph Palette.  To do so, I have to break out the Tools Palette and wield the Paint Brush (boring and tedious, especially when compared to wiring a single Color Box to a set of Properties).  Can we get the "missing Color properties" made available?

 

The Figure shows the original Grey Chart, the result after wiring Yellow into the Frame Color property (note that there's still a lot of Grey, including underneath the X Scale values -- this is fixable), and the third shows what I'd like to be able to accomplish with additional Property nodes made available.  It is frustrating to able to color Frame, but not the "Extras".

 

Plot Coloring Idea.png

Bob Schor

The default formating for numerics is automatic with 6 significant digits and hide trailing zeros. I'm sure someone thinks this is a great format, however I would like the option to specify default numeric formatting through the ini file. It would be great if this could be applied to the default font for the numeric also.

Bookmarks should NOT be created unless the first character after # is an alphabetic character. http://zone.ni.com/reference/en-XX/help/371361N-01/lvhowto/manage_tasks_lv/ says "hashtag followed by text is called a bookmark." Although it says # followed by text, it is not only creating them from alphabet characters but also numbers and symbols, e.g. "ID #132", "(###-###-####)". The number of unintended entries in the Bookmark Manager can render the feature almost worthless, especially when upgrading from 2012 or earlier. There are so many non-bookmark values that the presence of any real bookmark (e.g. code to fix) is lost like a needle in a haystack. I know others (e.g. QFang) liberally use "#" in controls, indicators, descriptions, comments, etc. as shorthand for "number" or "number of". There should be few objections since digits and symbols can be in bookmarks after the first character following #.

A pretty common use case of LVCompare in my workflow is to use it as a diff tool in SVN to compare different versions of a VI. When I do that, the previous version is downloaded into a temp directory, and then there is a decent amount of load time because dependency paths have to be resolved differently for the version in the temp directory and some recompiling happens. For top-level VIs in large applications, it seems like the whole dependency tree is getting loaded, which takes a long time. But really, for comparing VIs, there's no need to load the contents of lower level subVIs (and their dependencies, and dependencies of dependencies, etc.) As long as the connector pane, typedefs on the connector pane, and the icon of a subVI are loaded, that should be enough information for a visual diff of the top level VI.

 

 

                                                            Find and Replace

 

                                Type in the world(s) to search for   >>  recent words

 

 

 

toto.png

The updated to IEEE 754 adds a half-float and a platform independent quad float. We have a project where a data source will be giving us values in half floats (16-bit). It would also be nice to support quad floats (128-bit) since the current EXT datatype is platform dependent.