Michael Aivaliotis

Check out the VI Shots interview I did with John here: Extending LabVIEW to the Web with LabSockets

Wow, someone revived this thread. Hey, we only had to wait 10 years for a built-in solution... Sheesh.

Darn, you beat me to it.

A follow-up to this issue. I've released a new version of VIPM that resolves the crashing issue reported in this thread. It can be downloaded on the VIPM Labs page.

This is not just an OpenG problem. This is a general issue with anyone creating and packaging reuse libraries. I think putting OpenG items in libraries is the best approach and is also the one recommended on the palette guidelines doc here: https://decibel.ni.com/content/docs/DOC-29567

Actually, not enough cooks. We all are.

If you were lucky enough to come to my NIWeek 2013 events presentation, you would have seen this slide which I put up as an icebreaker. No, this not photoshopped.

Seems like a deficiency in Quick Drop

Congrats!! - Next stop, CLA.

What do you want the text to say?

I suggest you all start using the new Event Inspector Window. On the left-most column you'll see a sequence#. This is a globally unique number that each event has and is used to order the events. This is a new (behind the scenes) feature of LabVIEW 2013 that guarantees that events now will always be handled in the order they are fired.

Is there some way to force the use of class data accessors to access class data for class members? My use case is I simply don't want the use of unbundle node to be used. I like to massage the data (sometimes) before it's accessed and want to make sure developers and users of the data only access it through the accessors (VIs or Property nodes). Perhaps there's another way to enforce this? Note: This need is for members within a class, you can't do unbundle outside the class already. This also raises another philosophical discussion on the decision between VIreadwrite vs propertyreadwrite. What are the best practices for this and what are the factors in deciding one over the other?

LabVIEW 2013 has crashed twice on me so far. Sorry...

For references and more information, see worrydream.com/dbx Presented at Dropbox's DBX conference on July 9, 2013. Bret Victor -- worrydream.com http://vimeo.com/71278954

Here's a mental game. In the promo video, just replace the word noflo with LabVIEW. http://www.kickstarter.com/projects/noflo/noflo-development-environment

Do you guys really use FGV or AE much anymore? I would think it's a dying practice now with native classes.

Only got 3 of them recorded: https://vine.co/v/hbQKIF2V62U https://vine.co/v/hbQKPQHTp3g https://vine.co/v/hbQAui2OlDU

Thanks, I added it to the list.

Unfortunately, i did not get to see your presentation because it was at the same time as mine However, I will devour Mark Balla's video of it. The feedback I heard from others was that each of you (David and Staab) could have had your own dedicated sessions. So not sure how you can add more content. But I will reserve judgement until I see the video.

The new Events features is my favorite. I did a presentation on this topic at NIWeek. I started a new thread to spur discussion (i don't want to derail the current thread). I'd like to get the community's input on the new event features. New Events Features in LabVIEW 2013

I did a presentation at NIWeek 2013 on the new user event features in LabVIEW 2013. I will post a link here when it's ready for online consumption. For now, I'd like to start a discussion on what all the LAVA members think of the changes and additions. If you have questions on how one feature or another work, please post here and we'll get it answered. To summarize, here is what was changed, added: New - Event Inspector Window (you're gonna love this!) New - High Priority events New - Flush Event Queue Function New - VI Scripting methods and properties for events New - Mouse Scroll Wheel Event Improvements to the Edit Events Dialog: It's now resizable (Finally) You can filter search the list of event sources and events. For easy navigation. You can limit instances of the event in the static queue (Similar to Flush Queue function) [*]Finally, there was a behaviour change: Non-handled, dynamically registered events do not reset the Event structure timeout terminal. In LabVIEW 2012 and older: Non-handled, dynamically registered events reset the Event structure timeout terminal. Let's keep this positive. We all need to learn how to use these new features and how to integrate them within our frameworks. I know a lot of you are using user events as the main communication mechanism for your processes and modules. Let's figure out how to make our code better with all this new cool stuff.

If anyone knows Norm, you know how much hand waving he does when he gets excited. Well, the Leap Motion got hand wave overload

fixed

Just found out about this "NIWeek tradition" https://www.facebook.com/events/678470302167587/

http://youtu.be/ASO_zypdnsQ