PaulG.

Are you including your called subVI in your build specifications, i.e. you have your startup vi but your called VI needs to be under the "always included".

QUOTE (jones @ Sep 24 2008, 04:49 PM) No.

QUOTE (Michael_Aivaliotis @ Sep 23 2008, 02:09 AM) You couldn't pay me to watch a Michael Moore film. :thumbdown:

Anything that allows us to make better looking front panels is a great idea. Working with control clusters is one of the least favorite parts of my job, simply because it is extremely difficult to get things sized and aligned properly. It has to be perfect. I have a lot of arrays of clusters and their sizes change during runtime. If everything isn't aligned and sized exactly right the FP looks like crap. And that is what the customer sees! I would think NI would realize this and work a little harder to give us the tools to make LV a little "sexier". Not all of our customers are engineers.

I tried yours and it behaves the same way for me. However, I re-created your VI and I can edit any comment in any case regardless of what the enum is set to. I live and die by enum state machines and have never encountered this before. However ... upon futher investigation it so happens that when I expand the size of the comment block itself it started misbehaving the way you observed. Very strange.

A bunch of physicists with a toy 27 miles in circumference using 10GJ of energy attempting to recreate the conditions of the Big Bang. No good can come from this.

QUOTE (NareshN@Capsys @ Sep 10 2008, 08:17 AM) It's a property that can be changed. Select the control on your block diagram, right-click, then select create>property node>label>font>size. Right click that and select "change to write". Then you can write the font size you want.

Error handling is a lifesaver - especially when used to monitor the status of any hardware. I can't tell you how many times I've gotten into "it's a hardware issue" "no, it's a software issue" discussions.

That's probably what I'll end up doing. It was fine this morning, but just before I started to build my application I start getting the error again. Argggggghhhh!!!!

More "noise" from me. But this is the Lounge. I'm not easily impressed by most music. But I saw/heard this tonight and thought it was beautiful and BRILLIANT. Who is she? Where can I find more? :worship:

More "noise" from me. But this is the Lounge. I'm not easily impressed by most music. But I saw/heard this tonight and thought it was beautiful and BRILLIANT. Who is she? Where can I find more? :worship:

QUOTE (Antoine Châlons @ Aug 31 2008, 11:16 AM) I tried that. Didn't work. This issue is like being nibbled to death by a duck.

The Project IDE took some time getting used to, but now I don't think I could live without it. Previous to project it was a headache keeping track of everything else besides my code that I needed to build a complete application or an install disk.

QUOTE (crelf @ Aug 29 2008, 01:32 PM) Pick one. Every one I've worked on today. And it just so happens it's not doing it anymore. Everyone is leaving early for the weekend so it has to be related to the office network somehow. I'll see if I can duplicate it again ... but I ain't stickin' around either. Not even for LAVA.

I looked this up here and on the DS but have not found a solution. I keep getting a "Generic file I/O error. Cannot save VI 'xyz.VI'" From what I could glean it's network related and has been around since at least v8.0. I can go days without getting it, then one or two days out of a week I'll get it over 100 times. :headbang: "Save as" something else is out of the question. And copying everything from the network drive to the local drive is out of the question as well. Is there a patch somewhere to fix this? It's really annoying.

QUOTE (neB @ Aug 21 2008, 03:32 PM) "Sponsors"? What then? "The 12 Steps for LabVIEW-aholics"? :laugh:

Search the LabVIEW Help is your friend. There is a fairly extensive explanation of errors and error codes there. And I have it in my head that user error codes start at 5000, and no, I don't think it makes a difference if they are positive or negative. I just start at 5000 because it's easy to remember.

I think the native LV tip-strip is pretty worthless. As alread said, you can make your own. I've made a vi that "popped up" and closed a "tip strip.VI" that displayed the information in the tip strip when the user right-clicked within the boundaries of a control. I just shut tip strips off in my application and used my LV version of it.

QUOTE (Aristos Queue @ Aug 21 2008, 06:17 PM) Not guilty. :thumbup: QUOTE (JiMM @ Aug 22 2008, 07:29 AM) Somehow I don't think that the colleague that I inherited this VI from would appreciate (in BOTH definitions of the word) this conversation! MY EYES!!! That's HIDEOUS!

Yes. I noticed this yesterday. Something's going on over there.

Occasionally I will run an output from a subVI into a single frame sequence in order to probe it. STACKED sequences, on the other hand, should be banned outright!

I'm getting into a situation right now where this would be very helpful. But it requires 8.6

It's difficult enough dealing with real discrimination (race and age) you don't need to create new problems by asking irrelevent personal questions. After reading through this post I'll offer a suggestion: stick to the technical stuff.

I think LAVA has been hijacked? A joke, right? (nervous laugh) ha ha ha ... "air force one"? These look like clown shoes. Just about everyone I know disdains and is afraid of clowns now days. ROTFLMBO!!!!! :laugh: :laugh: :laugh: :laugh:

Very cool, indeed. It needs music, though. It reminds me of the dancing waters at the Bellagio in Vegas.