Michael Aivaliotis

Just an FYI on this topic. Some good news. Here is some insider info which confirms that this will be resolved in a future release (don't ask where I got this from).

QUOTE

LVDev1: I have suggested to [LVDev2] that perhaps we make the special case of saying that we allow dynamic object sizing (objects resizing during the drag) only for objects that are set to fit the pane.

LVDev2: Due to many reports of this bug fix causing problems for many people, I've added a new option to allow the 8.0 behavior on a per-pane basis. On the pane's popup, select "Objects Scale While Sizing" to make the objects scale live when sizing the window. The option is off by default since there are many layout possibilities where problems accumulate very quickly when live scaling is on.

LVDev3: Confirmed fixed in [next version of LabVIEW].

QUOTE(Aristos Queue @ Jun 9 2007, 02:35 PM)

LabVIEW classes know how to translate old versions of themselves into the current data format.

Does this work in an executable?

The key is the generic file header that can always be accessible by any reader. Once you determine which version of the file you are reading, you would then need to select the appropriate datatype to use.

To get computer name:

Everyone. Please switch any threads to Standard Mode until this issue is resolved.

QUOTE(Val Brown @ Jun 7 2007, 03:20 PM)

If a required input/connector is not wired then you get a broken wire -- meaning, among other things, that the LV code can't be "compiled". I think Tomi got it right -- without a required input/connector a memory buffer is allocated.

Well, I think that's stating the obvious. If you DO have the wire connected however, and the input is marked as required, then what? Does it make a difference?

QUOTE(Tomi Maila @ Jun 7 2007, 02:11 PM)

It may very well be true. In theory required inputs can be optimized better at compile time of the VI. For not-required inputs VI needs to create a memory buffer for the particular input. For required inputs VI can more easily reuse the input buffer.

This doesn't make sense to me. A required input just indicates to the user that they need to connect the wire. The only difference I see is that in one case the wire is connected to the input terminal and in the other case it is not. Perhaps this makes a difference, however the "required" flag by itself does not carry any valuable info for the compiler. Of course, there may be some black magic that only NI knows but at face value, I don't see it.

You can download a free utility that updates your wallpaper automatically just google: automatically change wallpaper to see a slew of freeware tools. If you type ipconfig /all in the Windows Shell command, it will return all you network card info.

QUOTE(BobHamburger @ Jun 3 2007, 09:30 PM)

4. I searched the forums here using the terms IMAQ and USB. I found lots and lots of postings, but I can't seem to read any of the thread replies! I can get to the original postings, with a tree of replies underneath. Clicking on any of the links to replies goes nowhere.

Click on Options>Standard

http://forums.lavag.org/index.php?act=attach&type=post&id=6009''>http://forums.lavag.org/index.php?act=attach&type=post&id=6009'>http://forums.lavag.org/index.php?act=attach&type=post&id=6009

QUOTE(yen @ Jun 3 2007, 12:44 PM)

Now it doesn't work.

So i guess now is fine?

QUOTE(yen @ Jun 3 2007, 08:52 AM)

It's actually back to working fine for me.

Which browser do you use?

How about now? Does it still work? There are some settings on the forums that cause this and I'm trying to find the combination that causes it. It always works for me so I can't tell myself.

how about now?

QUOTE(John Rouse @ May 30 2007, 10:32 AM)

Why is it so difficult to get really good (in depth) learning material about LabVIEW and why after all these years and versions (not to mention the cost of LV ownership) are there as of this day only several published books even worth reading about LabVIEW?

Im not talking about NI help or on line resources which are fine for when you are programming, Im talking about the "real" stuff;

The stuff that you can actually learn from. Old timers call it Book learning.

I've learned more from one decent about LV in 6 mo than in over 10 years of looking at all of NI's help files, web content, Discussion forums etc etc and that includes many courses given by NI which are (IMO) little more than exercise books.

NI s help is sufficient but lacks depth. There is no depth to any of NI's teaching, on line aids and such. why is this so and what could NI ultimately do about it?

Don't want to stray the conversation off-topic (great questions everyone , btw). I don't think there's money in LabVIEW book writing. Based on this blog, why would anyone spend the time to publish (besides fame of course)? I think all the old timers with knowledge to share should put efforts in resources like the LabVIEW Wiki where we can combine our resources instead of isolating ourselves. Why should NI be responsible for good books when there are a lot of us out here with knowledge to share. One of the reasons I started the Wiki was so I can have a platform to write my own in-depth articles. Like anything however, it takes time.

Is it ok now?

I'm not sure about the other stuff but the long build time is probably due to the "Remove type definitions and unused polymorphic VI instances" on the Advanced tab. Un-check that and try again.

If you want to hang out with the LAVA crowd then the Radisson is the place to be.

QUOTE(pockey @ May 29 2007, 06:38 PM)

Hey, my supervisor asks me to find a method to read and record the sound card. Is there any example in LabVIEW to realize this?

Thanks in advance!

Try this: http://www.google.com/search?hl=en&q=labview+sound+card&btnG=Google+Search' target="_blank">LabVIEW Sound Card

LabVIEW 8.2.1

When working with any XControl. If you right-click on the xcontrol instance and select show>caption, you will see an ugly black caption with no way of making transparent. Also, if you move it around you see ugly black shadows. Hs been reported to NI, waiting back.

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.