Michael Aivaliotis

Just a reminder that all the cool cats are hanging out at the NIWeek 2008 Forum. If you have an event to publicize do it there.

So sad... "SuperFunkyPrivateSpecialSecretForumStuff=LAVA" doesn't work anymore. I say we boycott LabVIEW8.6.

QUOTE (Justin Goeres @ Aug 1 2008, 12:35 PM) Of course you don't wash your LAVA T-shirts. You dry clean them of course. I always like to store mine in one of those air sealed bags with a pack of silica gel inside for good measure.

QUOTE (Aristos Queue @ Aug 1 2008, 02:20 PM) Isn't that a typo? Shouldn't it read: "that might result in fewer broken class items"? Because fewer unbroken means more broken right?

QUOTE (jgcode @ Aug 1 2008, 04:30 PM) Why count down the days? ftp://evalftp86:LabV13w86@ftp.ni.com/LabVIEW_86_E.exe' target="_blank">Download LabVIEW 8.6 here. Just use your current SN.

QUOTE (crelf @ Jul 31 2008, 02:18 PM) That's what she said.

God I love LV7.1... Here's an easier way:

So I screwed up. Apparently only Premium Members can send attachments via PMs (who came up with that one?*) so instead of PMing me the image just post it to this thread. Thanks. *I did

Oh god, here we go... If you want to add your school flag then send it in a PM to me. Make sure the size is 32px width by 20px height. Also make sure to state the full school name. Feel free to also post it here on this thread (to hash out the image specifics with your friends), but I probably won't see it for a while.

My suggestion for the future is to order a mens size. Small would be good for Crystal and Medium probably for Christina. Of course I'm shooting myself in the foot by discussing body sizes with women :ninja: Also, I have 7 medium LAVA (superfunky) T-shirts from last year that I'm bringing. So I can gladly give some to you guys that need shirts and don't want to feel left out. It's probably cooler Christina since it has the secret ini key setting that you added to LabVIEW. Also, it's probably too late to order a shirt now for niweek. For some reason dark shirts take up to 3 days for production.

I'll be with the JKI team as always Sunday to Friday Morning. I suggest you all track me on twitter here. It will be a lot easier now that I have my iPhone. I'll be twittering very often on my whereabouts during NIWeek. This year is going to be crazy for me. Also, one of the issues with doing presentations at NIWeek is no matter what I do, the presentation will never live up to attendee expectations. That's a fact I have to accept. So if you want to come and see how some of the cool UI features in VIPM were done, come on over.

QUOTE (Norm Kirchner @ Jul 28 2008, 11:24 AM) Ditto on that. You should pass the User Event Refnum. Then just register your events at the event structure. You can have multiple event structures registered for the same event. Also, you don't really need to "pass" it. You can just as easily use a functional global that stores the User Event Refnum(s).

QUOTE (jdunham @ Jul 25 2008, 01:39 PM) You could try http://wiki.lavag.org/LabVIEW_configuration_file/Miscellaneous#MRUFolders' rel='nofollow' target="_blank">this ini setting (MRUFolders). It helps a little. Don't know if it works in 8.5.

Thanks for posting the PDF. God I hate that NXTbooks or whatever it's called.

QUOTE (Norm Kirchner @ Jul 23 2008, 10:44 PM) You mean these drinking games?

LAVA is donating 4 Pink USB powered LAVA Lamps Whether it's a late-night coding marathon or just your typical afternoon staring at spreadsheets, the USB Mini Lava Lamp will help you relax. Just plug it into your USB port for power and this little desktop ambiance generator will do the rest. Filled with clear "lava" and a bunch of glitter flakes, this light creates something resembling a disco ball effect on your desk and walls. The USB Mini Lava Lamp is an authentic Original Lava Brand® product and comes with a single small lightbulb. It stands about 6" tall and connects using a coiled USB cable that stretches to about 4 feet. Also has these wonderful features. No batteries required - draws power from USB Includes USB cable Uses a single, small lightbulb Dimensions: 5.8" tall x 1.7" wide 90-day warranty

Wow, looking at the door prize list. It's just worth coming for a chance at those items. Good odds.

What emotions do you feel when you watch it? Original Link.

The part where I actually laughed was at the end where he brought up a slide of complex formulas in response to an audience question. That was the punchline for me.

In my opinion the code has to be clean and self explanatory. It's not enough that it works or that it has a great design. If it takes me just as long to refactor code as it takes to understand it then I always opt for a refactoring. At the end of the day, I will have become an expert in your code after the refactor, plus it will be easier to understand for then next person.

Is that site like the anti-wikipedia or something?

AQ, Did Ton's solution work for you?

QUOTE (Aristos Queue @ Jul 8 2008, 07:43 PM) I can't post the actual VI hierarchy that I'm seeing this in, but I will try to extract some code to see if I can reproduce. Also, I see this behavior in various projects I work with so it's not isolated to one case. This has also been reported to me by other colleagues at JKI so at least I haven't been smoking http://www.marijuana.com/homemade-paraphernalia/76706-making-vaporizer-out-lava-lamp.html' rel='nofollow' target="_blank">LAVA weed or anything. I have, however come across something else that might help. This behavior seems to only happen with the project environment. I tried opening the VI hierarchy alone without the associated project and the "save all" works as expected.

In a typical software application, when you perform a "Save All" action you would expect it to save all of your open documents or working files, right? Not so in LabVIEW. Apparently LabVIEW is not a typical application. Even though I ask LabVIEW to please save all my VI's. It doesn't. I can see that it doesn't because when if I open up a VI that is on the diagram of another visible VI, I see an asterisk in the titlebar indicating that the VI has unsaved changes. In LabVIEW 8.5.1 there are two "save all" menu items, one called "save all" and another called "save all (this project)". I've tried both and neither produces the expected results. It's possible that the behavior of the "save all" has changed over the last four or five LabVIEW versions. In the past, the "save all" menu function would save ALL vi's in memory. Regardless if the front panel is visible or not. I'm thinking that this is not the case anymore and now LabVIEW only saves VI's with their front panel visible. An exception to this rule is that LabVIEW somehow remembers if you've opened a VI with unsaved changes and then closed it (without saving changes) thus actually saving it when you later perform a "save all". Is all of this true? If so, then is there any way to perform the old-style "save all"?