Michael Aivaliotis

The Full details here.

LabVIEW 2009 f2 Patch Details

The LabVIEW 2009 f2 patch resolves the following issues:

ID Description

151665 Memory leak when using .NET callback in LabVIEW

178614 Type defined constant can lose value when updating to edited typedef if feedback node also on diagram

182053 Custom About screen not displayed with a LabVIEW built application

183560 Graph does not display timestamps on X-axis as expected when using timestamp data type

185219 Error 1502 while building a LabVIEW application

185348 VIs with very large type descriptors (like the Enum with 2000 items) will crash on load after being saved in LabVIEW 2009

185362 Timed loops using a timing source terminal upgraded from LabVIEW 8.6 to 2009 will function correctly, but incorrectly indicate the built-in timing source is used.

185980 Editing An Event Structure With A String Event Might Crash Localized Versions Of LabVIEW 2009

186276 Certain references (SoftMotion, WSN...) may incorrectly refer to data associated with a different reference

186418 Image Display control does not update using Value property node in a LabVIEW built application

186602 Application Builder uses too much memory, which may result in build failures

187759 Cannot launch LabVIEW 2009 when using Microsoft Mandatory User Profiles

Please vote for my Idea:

Add an "Explain Error" pop-up menu on the conditional error probe

I just want to jump on here again to bitch about this new "improved" Probe Watch window. I've just been through an intense LabVIEW debug session and have to beg NI, Please for all that you hold dear, add the ability to not dock the probes automatically!

Just so I don't have to wait until next August, put this in a 2009.1 release. Please, Please Please!

Yeah I use a Xbox 360 for media browsing...

Ya, I appreciate all that. The whole point of this exercise for me is, I just like tinkering and building of this stuff. I can always upgrade components as I see fit. Also I can add various tuner cards later and replace my cable box. So it's the process, the learning and playing around...

Stumbled across this which seems interesting.

This is the case I'm using. In Silver, to match my other components. I like that old school look. It's also the slimmest case on the market. Shallow too. But surprisingly fits 3 hard drives and a micro ATX board with a full PSU.

So I decided to ignore all your suggestions and went with this keyboard and this mouse.

I really need a real mouse because I will probably end up playing a few games on there. This mouse was chosen because I have a glass coffee table. The keyboard is minimalistic and small, and has a cool glowing backlight.

I already have a remote which came with the pc enclosure which has the directional keypad and the media center button. All the pieces are coming in tomorrow. I'll post pics up at some point with a video of course.

I have an update. I reported this to IPS and it seems to be a known issue that they are working on. See here.

I can now definitely say the problem still exists after the update.

So is it confirmed that the issue is only related to topics that you've replied to or does this problem apply even to topics that you have not replied to?

Ya, the Dinovo Mini looks really nice and compact. If only it had xbox360 support it would be perfect but not a big deal. I think that's the way to go. Cnet video review here: http://reviews.cnet.com/keyboards/logitech-dinovo-mini-keyboard/4505-3134_7-32784878.html

All the pieces of my HTPC are coming together this week and I'm excited to start setting it all up. One thing I'm not sure about is the what wireless keyboard and mouse to get. Since this is going to be in the living room I want it to look good. I also was hoping to get a keyboard with a trackpad on it so I don't need the mouse. Any suggestions?

The line that really got me was: "If there’s no unit test the customer isn’t going to complain about that.”".

Ya, I don't like that. Even if you duct tape, you should still test.

have you tried Jumbo frames?

I just updated the LAVA site to the latest bugfix release.

You'll also see a new Subscriptions tab at the top of the page. Those that don't already have Premium Membership and wish to get one can do so now through the LAVA site. If you already have a Premium Membership then you don't have to do anything until it expires.

Whatever you don't waste your time with unknown Ethernet adapters. Use Intel all the way.

As far as learning on the job. I disagree with learning on your own time. Your employer should pay for your training time. Even if that means letting you go off for a week to experiment with LVOOP on your own or by chatting on LAVA. Some employers don't allow that, this is why we see many people trying out new techniques on new projects. I've been in that situation. I had an employer you drained the life out of me to the point where my only reward for hard work was the knowledge I gained by experimenting with new LabVIEW features (used on projects of course). Yes, it was risky being on the bleeding edge sometimes, but I took calculated risks and I was the one who had to fix things when it went bad. And I always did.

Side-step rant:

As an old timer, I can tell you that back when I was programming in LabVIEW 3.11, we still got systems out the door and there were many alliance member companies that were building systems exclusively using LabVIEW and making successful businesses out of it. We didn't have event structures, we didn't have DAQmx, we didn't have LVOOP, heck we didn't even have multithreading. We just kept building systems with LabVIEW because no one told us we couldn't. I chuckle to myself when I read posts on the forum about how now LabVIEW is a real language people can finally use because it has by-ref objects or some other feature A or B. Some of the techniques you learn when you have little to work with, you take with you throughout your career.

Wow, that's what I want, and I'll install LV2009 now.

Huh? No need to wait. 2009 is a great product from the start. Install it now.

This looks like an awesome feature. Can't wait to see the results.

PS: as a premium member, my posts bypass the profanity filter. It took a lot of restraint to not demostrate that.

Actually wee haven't tested that, have we?

When I double-click a VI's icon in the top right corner and I have the front panel open, LabVIEW opens the icon editor without complaints. But when I do the same from the diagram LabVIEW opens the icon editor and it also complains by beeping. Why? Is it ticklish?

http://joule.ni.com/nidu/cds/view/p/id/1429/lang/en

Here's another feature request. When you right-click on the class wire, you get options to create new VIs.

Here's another version (for LV8.6) that sizes the panel to the size of the tree (based on the number of frames in the Case Structure) or the height of the screen, whichever is smaller. I like this so I don't have to resize it once it opens.

Can you update your official downloadto reflect your latest and greatest changes? Or is it not ready for prime time yet?

NI has started changing the status of ideas in the ideas exchange to "in-development". keep track of them here:

Ideas marked In-Development

New Ideas

Completed Ideas

OK, it's back to not working fine. I have two or three threads which don't appear in the unread list. I say take this to IPS.

They have a new bug fix release out which I haven't applied yet. I'll do that this weekend and we should look at it again after that.