Michael Aivaliotis

All of us here on LAVA wish you a speedy recovery.

The book describes how I used to program like 10 years ago. I later migrated to OpenGoop, Very out of date. It's very light on the OO concepts as well. Native LVOOP is the only way to go moving forward and this book doesn't help you get there. Not saying you can't use the methods described, but why would you when there are better ways. As far as the printing, I was lucky to get the first one out in 2003. So quality was excellent.

Where are you located?

It's apparently a known issue that is going to be fixed in an upcoming release. Thanks for reporting it.

I just reported it to Invision. Thanks.

There are two icons which you can use to link back to lava. Please link directly (do not copy to your site) to these icons: http://lavag.org/uploads/links/lava.png (80x31) http://lavag.org/uploads/links/lback-lava.png (88x31) These can be used by any other blogger or website as well.

Daklu, any chance for you to attach your code instead of just images?

I've seen this delay before, but not LV2010. I've seen this in LV2009. It happened only in one project of mine. I tried several things to debug it and came to the conclusion that it was due to the complexity of the VIs and not the entire project. Editing some VIs was faster than others. Here's a video showing this: <object id="scPlayer" width="375" height="268" type="application/x-shockwave-flash" data="http://content.screencast.com/users/Michael_Aivaliotis/folders/Hidden/media/3ad6b147-09ef-4725-aaf6-610d3485d736/jingswfplayer.swf"> <param name="movie" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Hidden/media/3ad6b147-09ef-4725-aaf6-610d3485d736/jingswfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/Michael_Aivaliotis/folders/Hidden/media/3ad6b147-09ef-4725-aaf6-610d3485d736/FirstFrame.jpg&containerwidth=375&containerheight=268&content=http://content.screencast.com/users/Michael_Aivaliotis/folders/Hidden/media/3ad6b147-09ef-4725-aaf6-610d3485d736/00000023.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Hidden/media/3ad6b147-09ef-4725-aaf6-610d3485d736/"> Unable to display content. Adobe Flash is required. </object> I don't know what all you guys are talking about. All of this feels like superstition. Don't walk under a ladder or else you get bad luck. Gimme a break.

I agree with you too! Why can't we prevent editing (changing the code) but allow copying and find all instances etc?

I agree with crelf.

I just want to see it. You can just attach it to the current thread as a zip file. Whatever you have. Edit: I just moved this thread to a different subforum.

Not the Block Diagrams you're looking for:

You can't imagine how happy you made me right now... I'd love to see this implemented. Is it possible for us to see some of the code? What are your plans for this. Perhaps post it on the LAVA CR?

Good idea Darren.

Stupid question. Why does your plugin class have to be in a separate project? Your statement: "To make it easier for people to add their own functionality to the program without having to dig into the full project" is not clear to me. Which class is the reusable component? Classes are libraries and libraries are by design meant to be reused.

So what's the real problem Ton? Do you have a website that's causing NI some problems?

Thanks to Tomi for introducing me to this: http://notinventedhe.re/on/2011-2-3

True, LabVIEW has limitations. That's why we're all here pushing the limits right? It's also true that you can have a successful lifelong career in LabVIEW and even run a software company that uses LabVIEW to its core, without ever having to touch a sigle line of text code. Oh, and it's fun too. The nice thing about all this: I never even once throughout the years doubted my decision to base my career around LabVIEW.

The thing with LabVIEW is, either you "get it" or you don't. Those that don't will never change, so don't bother. Our job is to try and find those that "get it" and help them grow. Hmm, that sounds like a religion.

For now it's stuff that I feel needs to be featured.