Michael Aivaliotis

Hey Alfa, you should update your profile image too, not just your avatar.

I looked at your example. My understanding of Object References is different. See Images. One issue to resolve with this method is dynamic dispatching. It seems that you can't do dynamic dispatching using Data Value reference terminals. Hopefully this will be added in a future LabVIEW release. In the meantime you will probably have to do dynamic dispatching inside the In Place Element Structure.

What version of Camtasia are you using? I'm using V6 and it works just fine for me. No issues. You can also try Jing which is made by the same company. Jing is just a recorder (you can't do editing) but maybe you will get different results. One more thing, in your Camtasia recorder options try enabling layered window recording.

The software demo's were done primarily with Camtasia Studio. The graphic animation section was done in Powerpoint and captured via Camtasia. I also had to do some Photoshop work on some of the images.

Yes, the LAVA lounge is currently open to serve you... All of us have strange sideline interests that can be tapped into. For example, I've made a MAME machine and I'm currently building an HTPC. I'm also getting pretty good and making videos for the web (I can help with gear, editing and publishing). I put together the latest VIPM video. Of course, most of us have to interface LabVIEW with actual hardware. So it requires knowledge beyond programming to get the job done.

I just posted an image. It seems to work fine. Have you tried the standard uploader? What browser and version are you using?

This is now resolved.

Note: This file has now been moved to the LAVA CR. You can download the latest here. Continue support discussions about it here.

He means the Block Diagram is password protected.

Wow, that's a good one. I'll look into it.

Works for me: <object width="444" height="282"> <param name="movie" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/jingswfplayer.swf"></param>'>http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/jingswfplayer.swf"></param> <param name="quality" value="high"></param> <param name="bgcolor" value="#FFFFFF"></param> <param name="flashVars" value="thumb=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/FirstFrame.jpg&containerwidth=444&containerheight=282&loaderstyle=jing&content=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/2009-08-13_2152.swf"></param> <param name="allowFullScreen" value="true"></param> <param name="scale" value="showall"></param> <param name="allowScriptAccess" value="always"></param> <param name="base" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/"></param>'>http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/"></param> <embed src="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/jingswfplayer.swf" quality="high" bgcolor="#FFFFFF" width="444" height="282" type="application/x-shockwave-flash" allowScriptAccess="always" flashVars="thumb=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/FirstFrame.jpg&containerwidth=444&containerheight=282&loaderstyle=jing&content=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/2009-08-13_2152.swf" allowFullScreen="true" base="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/42812b34-e8d7-4dfb-b1ba-f3e6649a8085/" scale="showall"></embed> </object>

The trick is to make sure that company A doesn't slap on a more restrictive license of their own. If you can't improve the code then maybe someone else in the community can. You want to make sure the license allows that. Speaking of NI's Instrument Driver Network. Can someone tell me what license those drivers are under?

Some interesting twitter stats.

This is not for 2009. Probably 2010. You can all sign up to be lead users for this and all the other cool technologies presented at niweek here. I would hurry before NI shuts down that page.

I think this is a big "Oops!" on NI's part.

By far, my favorite keynote demo: http://zone.ni.com/wv/app/doc/p/id/wv-1700/upvisited/y

You might want to check out this discussion.

Embed: <object width="480" height="385"><param name="movie" value=" name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src=" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="385"></embed></object>

This seems kind of extreme. It's also unnecessary. As long as the data relates to the state machine then it's valid to keep it in a local shift register. It also makes it clear to the observer, what design pattern you're using (don't tell me, you don't care about other people looking at your code right?). Using functional globals and file IO within the same VI to pass data feels like you're using the wrong tool for the job at hand. I don't see the benefits. Let me make this clear. I'm specifically focusing on data that is only valid in the context of the current state machine

Tons more photos posted from Lisa and Christian

Those that attended Jeff K's (The father of LabVIEW) Wednsday NIWeek keynote, saw a short video that included a mention of the JKI Right-Click framework. Someone just posted the full-length version of . Here it is: <object width="640" height="505"><param name="movie" value=" name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src=" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="640" height="505"></embed></object> Yes, that's Norm showing off LVSpeak.

I would recommend in the future to use the "insert code snippet" button in the toolbar. That way everything is preserved as intended.

I think I fixed this now try it again. You can now upload *.swf files

Well, the snippet is still useful as an image even though you don't have LV2009. My gripe is that NI could have added a text heading to indicate what LV version was used to create the snippet.