LabVIEW Idea Exchange

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

How come you can't tell which version a .vi was created in until you open it? How come you can't just tell whether it was created for 7.1 or 2010? An idea is to have it save a different .vi extention, much like in Microsoft Office, for exampe, a 2003 version would not open a 2007 version, and you can tell before opening because of the .xls or other extension.  For labview, it could be like for 7.1 it was .vi71 and for Labview 8.2, .vi82, and for 2010, how about .vi2010?

Maybe this could come in handy for those who are looking for certain vi's of a certain version.

I think the application builder should be able to generate a standalone applicationwithout the need to install the LabVIEW runtime engine, to reduce the user to install anduse the program to do the steps are too complicated or complex to install, or can becalled "hidden install" or "incidental installation", and will install all the files are placed in a program (such as VIPM installer). Best to install the non-LabVIEW files (like DOCdocuments, pictures, msi installation package, etc.).

Add power point added to the programs supported by the report generation tool kit. 

Many modules aren't compatible with Labview 2010 64 bit, but there is no warning of that before installing Labview 2010 64 bit. So the user goes through hour(s) to install the software, only to realize it won't work when he/she installs a module (Real Time Module for example), and then has to uninstall and reinstall the 32 bit version. If it isn't compatible, let people know so they don't waste hours!

It is 2011, and everyone is either making the transition to 64bit, or have already done so. Yet LabView on Linux is still stuck in 32bit, and this means that for modern Linux installations you have to install a ton of 32bit support libraries just to run LabView. Not to mention missing out on all the 64bit fun that everyone else enjoys these days, such as access to more memory. Please do something about this.

Currently in LabVIEW if you build an installer you end up with a hierarchy of files that look like this:

 

singlefile1.png

 

If you want to distribute this installer via the web, you need to use a third party program to zip it up, or create a self-extracting zip file.  Since LabVIEW can already create zip files with no problem, I propose the ability for LabVIEW to create a single file installer that can easily be distributed, like this:

 

singlefile2.png

 

This can be as easy as a checkbox in the current installer Advanced page:

 

singlefile3.png

Hi All,

 

I truly hope this hasn't already been inquired about in some manner, but if it has I'm not even sure what to search for.  Here it goes:

 

Up until now, I've kept a backup of labview.ini around so that if my computer dies or if I move to a new PC I don't have to spend time reconfiguring options.  It dawned on me tonight that there are a lot of other customizations that LabVIEW developers use.  If heavily relied upon, these customizations can be painful to lose.  For instance:

  • Palette customizations (Including "Place VI Contents" or Merge VIs)
  • user.lib
  • custom icon templates

...you get the idea. (This is a pretty lame list, but it's all I could think of off of the top of my head)

 

There really ought to be a tool to consolidate all of these options down to the nitpicking details so that they can be exported in the form of a single file. (let's say a zip file, hypothetically)  The user could then access this tool under "Tools-Advanced->Import or Export user settings" or some similar option.

 

This way, if the user's PC becomes unusable or they are forced by IT department mandate to move to another PC, they could simply import their user setting file and the whole development environment would be configured to their liking, complete with customizations.

 

Did someone already think of this?

 

Thanks,

 

Jim

 

 

To make my applications more portable across operating systems I've been using the OS's recommended directories to store config files and log files. Often this causes user confusion since they are used to navigating directly to the application's installation folder to find that stuff. I'd like to set up the installer so a link to the log file directory is placed in the application's Start menu folder.

Currently when you build an installer the current ini file in the destination directory gets overwritten. The user is generally unaware that this will happen and may lose configuration settings for their application. It would be nice if the user had the option to not overwrite the file during the installation.

For all NI software that has an evaluation license available I propose that instead of a number of days the evaluation would be good for a number of hours. Whenever the software detects user activity it will start to decrement the hours remaining. If no activity is detected after some number of minutes the timer will stop decrementing.

 

I installed the Test Stand evaluation and ran out of time even though I only got to play with it for maybe a few hours. I did get an extension from our sales representative. I am hoping I will get the time to thouroughly check out this software before trying to get funds from the boss.

 

This idea is not specific to LabVIEW but all NI software for which evaluation licenses are available. I am posting this here since the LabVIEW idea exchange is the most visible.

I have used Labview for about 10 years, the last 4 years complete full time as my actual job requires it, several times I have gotten a tired sight which made difficult to read Labview code, I really wonder if there are plans to add some zoom functionality.

 

In fact it would be nice to have a magnifying glass on the tools pallet, with a sort of resizeble frame that let you follow the code. There should be an rights explanation, because I feel this idea is kind of obvious, and also I am sure that tons of new users quit trying because this lack of functionanlity.

 

anyway let me know your comments,

 

 

As of this quarter, the NI developers suite DVDs will only be sent out on a bi-annual basis. See the text in the current Dev Suite donwload site for the text on this (Dev Suite Download Site).

 

With that in mind, I forsee using the donwload links to get my Dev Suite updates more and more often and using the DVDs less and less.

 

What I am asking is that a better method be implemented to allow customers to download the software that they need. If you attempt to download any package from the Dev Suite download site, listed above, you must click through between 3 and 4 linked pages to actually arrive at the download link. Given the 46 packages on the page that is a minimum of 138 pages that must be navigated to download Dev Suite.

 

How about updating the downloader to allow selection of all of the packages you wish to download, press the button and the downloader will take care of getting all of the selected packages.

 

This downloader should allow download of particular versions of the software (i.e All packages that were released with LV2009 SP1 and the applicable drivers at that time). These should be "presets" that would allow quick identification of which drivers shipped with which version of LV.

 

Jim Kring had a related post (here), however I think that the two ideas are somewhat different

 

 

 

 

 

It would be nice if there were an option for installer build specs that allow the user (who is running the installer) to run the installed application after the installer finishes running.  This would avoid the user having to find the installed application in the Start menu.

When running the NI Developer Suite installer, first detect what is currently installed (as the device driver DVD does) then display it in both the Licensed Product List as well as the Evaluation Product List. This way the user will not doubt what they have already installed. This way you can include option to "Leave this feature installed".

I did a search and did not find this. Hopefully it is not a dupe.

 

The event structure has become an almost integral part of LabVIEW programming. It should no longer be considered an advanced tool that is only needed in the full development system and higher. Events should be included in the base package. Maybe it means slightly increasing the cost of base and slightly decreasing the price of full. I don't know. But there should not be a LabVIEW that does not include the event structure. I own (my company owns) the development suite so I get nothing out of this. But if I were to buy my own copy I could almost see spending $1,249 but definately not $2,599. I am not going to spend over a grand for events and I am not going to program in LabVIEW without them either. So maybe someday, if this idea is accepted, I will get something out of it. And so will National Instruments.

 

Capture.PNG

 

When building an installer have the builder scan all .vi's in order to include all addition installers that need to be installed.

One of the biggest issues that I see new customers run into is the proper install order of LabVIEW and it's drivers.  It's not directly obvious to most that you HAVE to install LabVIEW before the drivers.  When they install another version of LabVIEW and do not update drivers, or they accidentally install drivers first nothing works correctly (DAQmx VIs don't appear in the palettes, New>Targets and Devices doesn't appear in the project menus, etc).  The solution to this is to completely uninstall the drivers that were installed, and then reinstall them.  This is annoying and takes a long time. 

 

My proposed solution would involve an easy "repair" option or tool that will simply reconnect the components and VIs etc to avoid the massive headache that most new users seem to get themselves in.

 

As of now, a Tab Control Page can be colored via Tab Control and Page property nodes. It would be nice if Tab Control Page Label can be colored, sized, and styled using Property Node. This feature should be incorporated in the future release of LabVIEW.

 

I am a big fan of LabView!  This idea is meant to be a positive suggestion, and I hope it will be taken as such.

I almost wish this post was in jest; it is not.  This is a serious suggestion that, in my opinion would improve the NI LabView program, save cost, and be much better for the environment.

 

I recently purchased Application Builder for LabView (both Great products).  I received my Application Builder via FedEx.  It comes in a very nice looking heavy mailing package with the bold label "NI LabVIEW 2010 Add-On Software.  I think there must have been a FedEx overwrap with the following forms:

-Printed shipping manager page with the FedEx Bar Code

-Printed packing Pick Slip (two pages) with a certificate of conformance on page 1 of 2 and a signed page 2 of 2 by the Vice President of Quality and Continuous Improvement (I am not making this up)

 

Now, inside of the envelope is

-The standard folded yellow installation instruction page

-A certificate of ownership! (same serial number as is printed on the outside of the heavy mailing envelope)

-A card which says (really!) "Where is my Media?"  The card says: "In an effort to reduce the impact on the environment, National Instruments no longer ships media with these kits.

 

Now, I assume by this point everyone sees the irony here, and where I am going with this New Idea for LabView!

 

IDEA: Upon successful purchase and proper payment of a LabView Add-On Software package: Email the serial number to the authorized user.

Optionally (if required by legal), send the paper Certificate of Ownership (one page!) to the authorized user, or if allowed by legal, Email a PDF of the Certificate of Ownership to the authorized user.

 

Savings:

Beautiful outer envelope and stack of printed pages made in Ireland - Well, not needed (Give them other work, I don't want to see lost jobs)

Shipping cost and impact on the environment (Ireland to Austin) SAVED

Storage cost and space at NI Austin SAVED

Shipping cost and Air Freight Austin to end user SAVED (less jet fuel impact on the environment)

Less paper to be recycled by end user SAVED, positive impact on less energy needed for recycling!

 

 

I propose that NI award anyone who posts an idea (especially this one) which is eventually accepted receive a free copy of the LabVIEW Developer Suite as an award for their creativity.

 

Should help find duplicates!