Michael Aivaliotis

I just got inspiration for my next LabVIEW front panel: http://yvettesbridalformal.com/index.htm Wow... PS. make sure your sound is turned up.... waaaay up.

QUOTE (Yen @ May 26 2008, 10:18 AM) Of course. We all know this is all a big hoax anyway.

QUOTE (netta @ May 26 2008, 10:36 AM) Huh? Don't get it. Please explain the reason for using LLBs. I use SVN and haven't looked into merging but diffing can be done. See http://forums.lavag.org/Programmatic-launch-of-compare-VI-s-tool-t10923.html' target="_blank">this thread. You should consider switching to SVN since you will get a lot more support on it.

First images are in. Wow what a surprise! Red rocky sandy stuff. High Res link.

Well, it's over. landing was a success.

click here

Or here.

QUOTE (rolfk @ May 22 2008, 02:24 AM) It's nothing bad. It just happens that the file has a evil sounding name. Apparently there is some bug in the forum that is linking the image to an old uploaded file. The zip file is just some LV code from another post. I will look into it.

NI marketing, take notes. How to get a lot of hits on Youtube. Classic line: "But you didn't drink that martini right?"

Here's a challenge for ya. Figure out how to control your home (or anything else for that matter) via Twitter and LabVIEW. Se here for some inspiration. Here's another shot, with video.

Epson's new display. I'm looking at what's behind it.

QUOTE (crelf @ May 21 2008, 11:09 AM) Yup, I was hoping to see it in the list but no cigar. How about OpenG?

Ok, so NI is always trying to be hip and cool (but of course we all know only LAVA members can claim that). This year NI is allowing you to select 3 badge avatars. It sounds cool until you find out that the selection options are pretty lame... and you can't add your own? I think we need to petition to allow adding our own avatar. Well, in any case, if the space is there, I will use it by sticking something on there of my own.

Compare Hierarchy

QUOTE (MikaelH @ May 13 2008, 03:03 PM) I tried this and it seems to do what I want. May I suggest this be added to the LAVA CR? It's pretty useful. QUOTE (tcplomp @ May 19 2008, 11:32 PM) And another option. The LabVIEW SCC VIs have an Compare VIs function. This one boils down into the following vi: vi.lib\SourceControl\support\SCCSup Compare Two VIs.vi: Looks like it is what you need. Ton I haven't tried this but it appears to have what I want too, however I needed SVN integration (can't you read my mind?). QUOTE (Christina Rogers @ May 13 2008, 12:59 PM) You might look at <LabVIEW>\project\procmphier.llb\CMP Compare two VIs.vi Standard disclaimers apply, e.g. about how NI can change VIs in the project folder without warning, yada yada yada. Wow, this will do what I want too! Hmm, looks like NI has some code duplication here. http://lavag.org/old_files/monthly_05_2008/post-2-1211312716.png' target="_blank">

This is a known issue and has been reported before. See here. If you think this behavior should change contact NI directly. Otherwise you will have to wait for Stephen to see this thread and then he has to agree with you and then he has to open a ticket. It's faster (and takes less arguing) to do it yourself. But you never know, today could be your lucky day. It usually takes at least two complaints over a span of a year or so for issues like this to get noticed by NI.

QUOTE (orko @ May 19 2008, 05:16 PM) What model is that?

QUOTE (Justin Goeres @ May 19 2008, 11:45 AM) Well, in that case it OK. Seriously, unless you are in First Class (which may be possible with your luxurious lifestyle), no matter what size laptop will be a pain on a plane. Just hope that the person in front of you doesn't decide to recline their seat (which always happens anyway).

Here's a VI Shots interview with Justin and his OLPC. Check out TurtleDraw. Very nice. Edit: It looks like OLPC is partnering with Microsoft. Gonna switch to Windows? Uh oh.

QUOTE (Aristos Queue @ May 18 2008, 07:37 AM) I was just about to post a rant about this very same thing. I found this a problem from day one. Not sure why NI never thought of this before 'cus it seems obvious to me. You want us to use the project environment don't you? For starters, why doesn't NI change the icon of the titlebar of the project window? That way you can find it and click on it easier from the taskbar. --- As far as the screen size, I think it's more of a resolution issue and it's not that simple. If you have a desktop screen then it's nice if both the desktop screen and the laptop screen have the same resolutions. if they don't, then large diagrams on the desktop will be overflowing on the laptop. Airplanes are not for programming. If you are programming on a plane, then change jobs. If you need to read a document or something then get a small laptop or hand held device. If I could get a 15" laptop screen with the same resolution as my desktop screen (1920x1200), then I would get it. If not then I'm not sure If I would.

Not sure why but can't download your attachment. Please upload again (using a simpler name).

QUOTE (Gary Rubin @ May 16 2008, 04:53 AM) Thank You! C'mon people. none of you have seen code like this? I think the hardware vendors should start outsourcing the development to LAVA members.

QUOTE (BrokenArrow @ May 15 2008, 08:17 AM) Re-Write? Uh oh, You're never suppose to use that term. Ever! It translates to: "You just wasted company time and money on a perfectly good piece of code" Remember, LabVIEW users "Optimize, Modularize and Reuse". Now go forth and practice these terms in your day to day conversation. For example: "I optimized that code we got so it's more modular and can be easily reused in our current and future applications". Now doesn't that sound more salary increase slash promotion worthy?

QUOTE (Yen @ May 15 2008, 11:16 AM) Yen, you need to lighten up once in a while. BTW, check this out... even Chuck Norris' cat can roundhouse kick: OK, so I had to post this... I couldn't resist, since you guys won't do it I will.

Perhaps "best" was too strong a word, but I think Classes need to be examined as a way of implementing hardware interaction.