Michael Aivaliotis

No need to wait anymore. Just watch the video and download the installer.

Watch this video to find out about the upcoming LV2009 Features: https://admin.na3.acrobat.com/_a56821929/p67979404/

So IPS responded that IE6 is officially not supported anymore since it's 8 years old and virtually a dead browser. I would agree, and I suggest you upgrade. Most of the web is moving in that direction. Sorry. PS. So if anyone has other problems and is using IE6. I suggest checking in other browsers before reporting the problem here.

What is your subscription mode set to for that topic? Immediate or Delayed?

Or how about a coding challenge, to draw the Mona Lisa with labview wires.

What exactly are you trying to do? Can windows talk to this already?

Does this happen when reporting posts in one specific forum, or everywhere? I'll look into this. It's most likely some permissions flag not set right.

This is definitely related to IE6. I've tried IE8 and Chrome but it's OK. I'll post it as a bug and see what happens.

Are they supersecretprivate agent VIs?

Hmm, I think for the majority of us, this is the default mode of operation. A project = my application.

The standard LAVA T-Shirt is located here.

I'm able to reproduce it in 8.6 if that's any help. It seems that the activex component data is seen as a change by labview.

Did you remember to pay your monthly internet bill?

I think the goals of this VI Preview should be limited to a specific use case and narrow in scope in order to be a realistic achievement. I would love to have a tool that we can use on LAVA to upload navigable VI images. We can't assume all LAVA members to be able to read your code in order to support your support discussion. Having these new images will help a lot. What would be the ultimate is to upload a VI onto LAVA and the server would convert it to an embedded flash. But I'll accept a tool for now. When can we expect a working version we can all try out?

Did this happen today or has it been like that since LAVA 2.0 went up?

Try now.

OK, I think I got it this time. Let me know.

That's great! BTW, LAVA also has an SVN repository here: http://code.google.com/p/lavacr/ You're free to use that. Also, it would be great to see your stuff on the LAVA CR.

There is no "decision" really. The feature you're requesting has to be built from scratch. If we were ever to implement it, then it would have to include an option for the member to opt-out of showing what they voted for. Are you implying that making votes public would increase the credibility of them? In any case, like any feature here on LAVA, it's mostly community driven so if the masses want it then we can make it happen. I was just expressing my opinion. You mentioned twitter. This is something you can opt-out of. You don't have to join twitter or display your twitter name on LAVA if you don't want to.

Hmm, I thought I fixed it. Let me try something else. Also, try logging off and clearing your LAVA cookies.

What do you mean by this? PS: Maybe next time you should apply for the Beta program.

That's because that thread was never imported. It looks like it was in the product announcements forum so it probably got dropped is my guess. I'll have to make a note to go and look for those. BTW, you'll have better luck using the LAVA search if you enclose text in quotes. I know, that's dumb. I'm considering adding back the old lava search which I had added using the Google search engine.

I think it would be nice to be able to locate the top voted posts. That would be worth implementing. I'm not in favor of adding features that would allow others to track member behavior. For example, I've disabled the forum features that allow you to track which member is looking at what forum, what post and is browsing who's profile (actually this last one is user configurable). I'm in favor of a little privacy when it comes to this sort of thing.

I don't think NI wants developers using VIs that are not in the palette because then if they decide to change some core functionality then your app will break, because they only officially want to manage functionality exposed in the palettes. NI doesn't want unhappy customers with broken code. But I'm sure you've heard the lecture from Aristos, haven't you?

A splash typically solves this problem. This should contain a dynamic call to your main program. You should try not to have any other subVIs in it besides the dynamic call. Keep it very light. You should also display the front panel of the splash first, then do the dynamic call.