Michael Aivaliotis

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

Yes, correct.

A follow up to this. I've added this feature in VIPM Pro. It's not available in the public release but you can get it in our VIPM Labs section here: http://support.jki.net/entries/24071293-VIPM-Labs . Even though it's not a public release, we are fully supporting it just like any other release. Just wanted to make a correction. The licensing and activation toolkit from NI is free.

JKI will be releasing VIPM 2013 for the Mac soon. If you want to try a preview release, you can download it here: https://jki.box.com/s/d3ux8pknhu39znpc0re8 It supports Package configurations, building, repositories and The LabVIEW Tools Network. All the same cool stuff that the Windows version has. The power of LabVIEW allowed us to use the same code base for both Windows and Mac versions which was pretty awesome. Let us know if you have any issues.

In order to get VIPM running again, you just need to install the LabVIEW 2011 run-time engine. You can get info about this here: http://support.jki.net/entries/20959253-LabVIEW-RunTime-Engine-for-VIPM If that doesn't help. Send an email to support@jki.net and JKI will open a one-on-one support ticket where we can get this resolved. This issue is on our (JKI's) radar for VIPM 2013 and will be fixed in a way where you won't have this problem anymore. In regards to the other comment: "I'm concerned that if I ask NI about VI Package Manager, they'll bounce me over to JKI, and the reverse if I ask JKI about it." - I want to say that both JKI and NI take customer support and problem solving very seriously and we will always do whatever we can to get problems like this resolved. So don't be afraid to ask.

works for me

Need a solution for LabVIEW on the Mac. I'm looking for a way to list all running Mac apps. Then I want to pick one of them and issue a quit message and have it exit gracefully. Does anyone know how to do this on the Mac?

Please do not report any of these issues to this thread anymore since the problem is already quantified by me and I am trying to address the root cause. The problem is intermittent and when it happens, I can fix it by repairing certain tables in the database. If you notice this problem, you can Skype me at michaelaivaliotis with a short message stating that LAVA is down. I will then promptly fix it. But don't expect a response on Skype acknowledging receipt of the message. You will just see LAVA work again.