Michael Aivaliotis

If you could ask anyone at National Instruments any question. Who would you ask and what would the question be? (Except this question: What is the password for the locked diagram of VI xyz.)

The simple answer is NO. LabVIEW does not have a native built-in feature to do this. However, with a little duct tape and some chewing gum you can do anything. Here's how: (LabVIEW 8.2.x) http://forums.lavag.org/index.php?act=attach&type=post&id=5950

alfa, you need help. I mean seriously. Stay away from weapons of any kind and go get some good psychotherapy.

The simple answer is NO. You cannot dynamically create splitter bars if none exist. You can, however, operate on them programmatically after they've been created. Right-click on a splitter and select Create>Property.

I uninstalled 8.0.1 (took 45min.!). Anyway, after a clean reboot: 821 startup: 2m30s. Closed 821 then re opened it: 821 startup: 30s. Worked on a project for an hour, then closed 821. Then reopened it: 821 startup: 1m

Well, I just finished upgrading an "old" 8.0.1 project to 8.2.1 so I don't have a need for 8.0.1 anymore. I'll uninstall this and see if it makes a difference.

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 did not clock the 8.2 startup time when I had it before the upgrade. Sorry. I'm not about to downgrade. It felt like 30s.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.

QUOTE(LV Punk @ May 23 2007, 09:19 AM) Ok, now I see it too. Thanks. I'll move this to the bug forum.

QUOTE(Tomi Maila @ May 23 2007, 11:31 AM) Thank you Tomi for supporting LAVA with this challenge.

QUOTE(LV Punk @ May 23 2007, 03:57 AM) Outline works fine for me. Anyone else?QUOTE(Gary Rubin @ May 23 2007, 05:38 AM) Clicking on the "Last Post" link brings me to the top of the page on which the last post is located, rather than right to the last post. 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) Sorry, the conversation started off with 8.2 and you switched it to 8.0.1 so I missed that. In 8.2 however NI decided to make both extractable. Here are the 8.2 contents: Web Browser Version: http://forums.lavag.org/index.php?act=attach&type=post&id=5923 Full Version: http://forums.lavag.org/index.php?act=attach&type=post&id=5925 I don't think this changed much from 801. So as you can see, even the

QUOTE(Jacemdom @ May 22 2007, 03:35 PM) I could spend the time and figure it out, but you can also do this yourself. Just download both run-times. Extract them and look at the folder contents. You will see several clearly labeled msi install files for the full runtime which are related to various add-on features.

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.

QUOTE(crelf @ May 21 2007, 06:50 AM) Sometimes I have to remind myself that there is a real person writing these posts...

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) That works too.

QUOTE(chrisdavis @ May 21 2007, 06:14 PM) I agree. Since the LabVIEW 8.0 release, NI decide to add a little confusion by creating two run-time engines. The old run-time is now called the "web browser only" runtime: QUOTE There are two downloads that are available. You only need to install one of them. 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.

QUOTE(chrisdavis @ May 16 2007, 06:44 PM) Question for you. How are the additional msi files included? Are they a post or pre install task? Also, upon an upgrade, what happens when the additional msi gets called again? Do you get the repair, or uninstall dialog for the msi?

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) Again, many ways to skin a cat. Your approach will work fine but there is no way to control the timing of the reads. They will happen asap which may or may not be desirable. I suggest you add a shift register with a timer value to control this better. Since the reads happen independantly from external commands, you need to put something that will trigger them. Some code in the timeout case of the bottom loop that sends a read command with a timer should do it.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.

QUOTE(Darren @ May 18 2007, 08:00 AM) The idea behind this is that viewing the results will probably bias your decision thus you give up your right to vote. You can vote then view the results or you can view the results only and not vote.