Michael Aivaliotis

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.

So another Mac issue. Whenever I try to use the ZLIB Store File.vi, I get an (always helpful, generic File IO) error. See the screenshot. Can someone (Rolf?) help me with a workaround? I need to stick with the OpenG Zip library because of the low-level VI's it provides, which are very powerful.

The following VI is part of the OpenG LabVIEW Zip Library: ZLIB Specific Path to Common Path__ogtk.vi If you notice, the case structure supports Mac OS, but not Carbon. The App.TargetOS output is Carbon. I'm running this on Mac OSX 10. This has a ripple effect in that I cannot use some of the Zip tools to compress files on Mac. Not sure who will be fixing this, since JGCode is on hiatus. But I'm reporting it here for the Googlers of the future.

Done

Would this work?

Sorry about not getting back to you all. The upload issue is fixed. So Ton, feel free to upload your new add-on tool .

Thanks Darin for the response. Ya, figures I'd run into a corner case. All is good now.

Awesome thanks. I think I figured out why Application Instance Close? wasn't working for me. So the WM_CLOSE message requires a handle to a window name. My executable had a custom window name. I was using this as the window name. So the window was closing fine but the event was not firing and the app remained in memory. In your example, if you set the VI title name to CloseMe, instead of the default CloseMe.vi, then it won't work. So the message gets sent to the window instead of the app, which is also called CloseMe.exe. Now I just have to make sure that my window title doesn't match my exe name.

The Application Instance Close? event doesn't work. If you can attach an example that works, that would be nice, but my tests show it not working. You're correct in catching my bug. Nice to have a second set of eyes . That was the problem. After I fixed that it worked as expected. So the updated diagram for anyone else needing this:

How can my LabVIEW EXE application handle the windows WM_Close message correctly? I have tried the Windows Messaging Queue library without any resolution to this problem. The behavior I'm seeing is that my application window closes but the app remains running as can be seen by looking at the process list in Windows Task Manager. The images below don't show it but I've added the Quit LabVIEW function to exit the app. So far I've tried: Creating a loop that monitors the windows message queue: Application Instance Closed? Event: Panel Close? Event: I've read this thread but it didn't seem to address the issue head-on. Or I didn't see what the resolution was. Any help is appreciated. Thanks.

I'm going to learn LabVIEW. So I can come to NIWeek with you.

This is why LAVA exists. Love it!

Ok, just got notified of this post. I'll fix it as soon as I can. Sorry about that. I have no idea what the problem is but no worries. I'll fix it. Thanks for you continued support of the LAVA Forums.

So one time we had the LAVA BBQ, I noticed that the establishment had posted the following sign on the door to guide guests to the right place: I wonder where the heck they got that idea from. Now I know: http://www.l-a-v-a.net/

Ya, thanks. Was on my list to fix and now it's fixed.

The certification team should also keep tabs on this board.

So it seems that Jack is having a problem building a package with Friend Classes and applying password protection using VIPM. VIPM applies passwords to VIs and libraries using standard LabVIEW VI Server calls so not sure what the problem is. I've filed this as an issue that I need to look into and will probably be calling on NI for validation.