Michael Aivaliotis

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

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?

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.

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.

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.

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

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.

This is really bizarre! Test Link Test Link It's a forum bug. I've reported it to IPS support.

I've created a new Code Repository Category under LabVIEW API called JKI Right-Click Framework Plugins. How the code repository works. How to submit code to the code repository.

A more detailed bug reporting process is documented here.

You know there's this browser feature called a bookmark.

This thread makes no sense to me. Maybe it's a cultural misunderstanding. So even if NI gave you a license then you would still have a problem? Why? Can this tool only run in the development environment? Must the end users have the full development environment to use it? Can you build an executable out of it? This will allow easier distribution of the tool.

I also want to point out another link that you can also use which shows you everything chronologically regardless of view: Once there you can then select the time window: This shows you read and unread content. You can distinguish the unread items because they have a different icon glyph status.

We haven't changed anything on our end for a few weeks now. It could be a bug.