Michael Aivaliotis

If you right-click on a file folder within a LabVIEW Project, you can select to "arrange by" type, name or path. This is all good an fun, however:

• When you add new files to the folder the folder doesn't re-sort the list. You have to re-sort the contents manually every time.
  
• There is no global setting for this. For example, newly created folders are not sorted in any controllable way.
  

This is bad.

Does anyone know of a way to add a folder of files to a LabVIEW project using filtering? For example, I currently have a use case where my folders contain svn subfolders which you don't really want shown in a project tree.

QUOTE(gmart @ May 23 2007, 01:17 PM)

I think we're missing a key metric. Where are the stats for the 8.2 launch time? I thought your original complaint was that 8.2.1 was slower than 8.2.

As far as everyone else. That's great, I'm happy for you (I really am) but how do I debug this? Any suggestions?

My stats:

LabVIEW 7.1.1: 30s

LabVIEW 8.0.1: 2m45s

LabVIEW 8.2.1: 1m30s

So, unless you can launch in 30s you're too slow for me, sorry.

I'm talking LabVIEW startup time without loading any VI's.

I see an outline with the original post, but if I click on any of the replies, I just see the original post. I just tried to view this thread in outline mode, and can't click on your most recent response to read it. I just see the first post ...

*Read, I'd do these by myself but I'm too busy so I try to leverage the power of LAVA*

QUOTE(LV Punk @ May 23 2007, 03:57 AM)

Outline mode seems to be broken this morning .

QUOTE(Gary Rubin @ May 23 2007, 05:38 AM)

Sorry, fixed now.

I just finished performing some speed optimization changes on the forums and other areas of the site. Please let me know if everything feels a little faster.

QUOTE(Jacemdom @ May 22 2007, 05:50 PM)

Does someone know what is the difference between the "Web Browser" version, that cannot be fully unpacked with winzip or winrar, and the contents of the "Runtime Engine" folder that is extracted from the complete package and with the path being LabVIEW_8.0.1_Runtime_Engine.exe\Products\Runtime Engine\lv80rte?

I don't think this changed much from 801. So as you can see, even the

Does someone know what is the difference between the "Web Browser version" LVRunTimeEng.exe 8.0.1 (24MB) and the "Runtime Engine" folder (20MB) included in the complete package 8.0.1 (87MB)?

I just want to revive this thread and say a big Booo! to NI for slowing LabVIEW down agian. After applying the new 8.2.1 patch my launch time sucks. Back to 8.0 startup speed.

Can you attach a new VI with your graph on the panel and a constant with data fed to it? I want to try a few things.

QUOTE(tcplomp @ May 21 2007, 06:46 AM)

I would add a high-speed (10 ms) seperate loop, and use the OpenG trigger VI to trigger the read action.

In this way you can add easily multiple speed triggers

QUOTE(chrisdavis @ May 21 2007, 06:14 PM)

the LabView 8.2.1 runtime engine itself is only 25 MB

QUOTE

• LabVIEW 8.2.1 Run-Time Engine (Web Browser Only)
  (24MB)
  
  
  is a smaller download intended for viewing Remote Front Panels in web
  
  
  pages. It does not contain the full run-time engine, but will allow
  
  
  some executables to run. This version can not be deployed. Download LVRunTimeEng.exe to install this version.
  
  
• LabVIEW 8.2.1 Run-Time Engine (Standard)
  (91MB)
  
  
  gives full support for executables. This version will support all
  
  
  executables built with LabVIEW as well as allow viewing of Remote Front
  
  
  Panels in web browsers. It includes support for DataSocket, Variable
  
  
  Engine and NI-USI. This version can be deployed using an installer
  
  
  created with Application Builder. Download LabVIEW_8.2.1_Runtime_Engine.exe to install this version.
  
  

So really, you may be able to get by with the web browser only version which is "only" 24MB.

As I've stated in other threads, I use http://nsis.sourceforge.net/Main_Page' target="_blank">NSIS and have been pleased.

Maybe we should start a new group called XNI? Thanks Jason for all your hard work and contributions to the LabVIEW legacy.

QUOTE(Eugen Graf @ May 18 2007, 08:42 AM)

It's okey if my read-task triggers itself?

Eugen

Another issue I see is you don't have an associated Write before the Read. What Write command will tell the instrument to return data? Unless the instrument is always returning data then I guess it's fine. In that case my timer solution in the previous paragraph is not valid. You need to do a check bytes at port in order to see if a Read is necessary.

This is the only on-line survey I've ever encountered where viewing the results counts as a vote.

QUOTE(NI Support)

The problem you are seeing is due to the fact that some component that the NI-Serial driver relies upon was installed from the November 2006 driver CD, and was not reinstalled by the February 2007 driver CD. This means that, in order to include the driver in an installer, you will need to supply the November 2006 driver CD in order to allow the appropriate component to be pulled from it. This is a pain point that we are aware of, and R&D is working to find a solution to this problem.

So it turns out that the best way to resolve this is to uninstall ALL drivers and install the one I want before the build. Does anyone else see problems with this methodology? I mean, let's say for instance that you are supporting multiple projects with differnet driver version requirements. What then? If anyone's gone down this path, do you have any suggestions?

When building an NI installer, you can specify additional installers. How does this list get populated? Does it depend upon what you have installed already? How do you specify a different version? Must you install that specific version in order for it to show in the list and include it in your installer build? I have a specific issue:

I see in my list that I have NI-Serial 3.2 installed and available. When I do the build, it prompts me for the driver CD which I provide. Even though the version of NI-Serial on the CD is the same as the one shown, it does not accept it. I'm giving it Feb 2007 - Disk2 but it asks for Nov. 2006 - Desk2. I even tried to uninstall NI-Serial and re-install the one from my CD but no-joy. I even tried copying the source NI-Serial folder from the CD to my hard drive and pointing to it but it still did not like it. It complained about not locating {GUID}.

Question: Why can't we just point to the #$%$@&! NI *.msi files we need?

Note: NI support has been contacted.

This is somehow related to this post:

Autosync a project folder with a folder on disk

I'm trying to build an installer. I want to add a Help folder using my installer. I would really like to use NI's installer but, yet again, I have found a limitation which causes me to look for other solutions (when will NI "get it"?). In any case, perhaps I'm being too quick to judge .

I would like to specify a folder in my installer that will be copied to my destination. It seems the only way to do this is to create it first in your project file then specify to copy this folder in the installer. This is an acceptable option. There is a limitation however. My Help folder contents change dynamically. Anyone who's generated an html help understands this. This means I would have to do an add folder contents, remove folder contents, over and over again (or before the install build). This is very tedious and prone to me forgetting to do this.

This is just one example of dynamic folders. Does anyone have a solution or workaround?

ya, the "--" don't work. Just enter a fictitious date instead.

No idea. Just remove the subscription.

Interpreting web standards isn't my job, thank god, but I think it depends on what version of the standard the browser chose to recognize and how much of it.