Michael Aivaliotis

I just wanted to give you all notice that the LAVA website will be going through an upgrade process within the next couple weeks. I don't know for sure when. But if you suddenly see things looking very different, then it's because of this upgrade. Some people will love the changes while others will hate them. The nature of LAVA is not changing. Just the code that LAVA runs on. LAVA will still be free and ad-sponsored and all of that good stuff is staying the same. So if you see problems and things that look out of place. Or if you just want to voice your opinion. Let me know in the comments below.

I suggest changing your workflow. Do all your work in virtual machines. Each virtual machine is one project. So switching between projects means, switching virtual machines. This is what I've been doing for over 10 years now and I'm a more sane person because of it. I still use VIPM because it's the quickest way to install a bunch of tools for a project. But after my tools and libraries are installed. I'm done. When I worked at JKI (a year and a half ago), I was involved with VIPM product management and development on a daily basis. At the time, I considered many new features. Allowing installation of packages inside custom project directories was on the roadmap. Mainly because, as a product manager. You do product marketing. It's what you do. And the product marketing told me that a growing number of customers wanted this. The trick is. How do you expose these two different workflows in your product? On the one hand, you install in this global location. And on the other, you install under a project folder. How about a combination of both? How is this information presented to the end user and how do you make sense of it all? And this is just the tip of the iceberg. There are several other consequences that ripple out from this, that I won't get into. When VIPM came out over a decade ago, only a few in the minority knew what reuse meant in the context of LabVIEW. Some would argue that people still don't know how to do reuse in LabVIEW. So VIPM not only had to survive as a product but also JKI had to educate the population on how to do reuse. In this context, it was best to keep a single workflow and be consistent: Reuse libraries start off as source code. Which can use any SCC technology. You do a "build" of the reuse library into a package. You install the packaged VIs into LabVIEW You use (link to) the installed VIs in your project source. Which also uses SCC. In order to change the reuse library, you must go back to step 1. Make a change, commit to SCC and then go to step 2, etc. It works. It really does. Whether you like it or not, is a different story. VIPM works the way it does because LabVIEW works the way it does. All of the VI libraries and add-ons that install with LabVIEW are beneath LabVIEW. If you open a VI, it automatically links to stuff beneath LabVIEW. For a newbie, this is great. But for someone who wants strict control of their code, this is a nightmare. VIPM provides a solution within this existing operating framework and does a great job. VIPM promotes and encourages the guidelines set forth by NI. As Rolf mentioned. LabVIEW projects (folder of VIs) now work in the context of LVPROJ and LVLIB files. This has fundamentally changed the world that VIPM works within. Over the years VIPM has adapted to this change. But even with these changes. The fundamental concept of reuse libraries has remained unchanged within LabVIEW. You can't "install" VI-based libraries in different project contexts. So in addition to asking for a VIPM alternative. You should also be asking NI to change how LabVIEW handles reuse code. PS: It's nice to see discussions have finally shifted from. Why should we do reuse? to How can we do reuse better?

All the OpenG stuff is now handled by this forum.

Does anyone have a solution to detecting where a drop occurred on a target tree control? I'm already familiar with the 'Point to Row Column' method. However, that only returns the row of the item you mouse is hovering over during the drop. See, when a user moves his mouse around, a line is shown exactly where the insert will occur. However this line location, between rows, is not available from what i can see. Regardless of where the line is drawn, the 'Point to Row Column' method returns the mouse hover location instead.

Perhaps there's an error generated somewhere that i can probe?

This is is LabVIEW 2015. Haven't tried in other versions but I assume it also fails as badly since it's not really a LV2015 feature. Here's my dialog configuration: Basically what happens most of the time is it just creates the property folder and 2 read\write VIs that are incompletely scripted: I have to remove the property folder and the VIs from the class and redo the dialog. Sometimes 3-4 times before it finally works. There doesn't seem to be a pattern to this. Has anyone else experienced this? if so, I guess I should report it to NI. If this is already mentioned on another thread, then sorry for the noise.

Still looking for more door prizes. Please post here if your company will offer a door prize.

Early-Bird pricing ends this Friday. Buy Now!

I think we need to make this our theme song: https://www.youtube.com/watch?v=GzZezqJ9VgI Full Song:

Greetings Friends of LAVA, colleagues, cohorts, and Wireworkers Extraordinaire -- it's LAVA BBQ time! click here >> LAVA BBQ 2015 Event Page: Register and purchase tickets (Show us the ticket code on your phone when you arrive or print it out) Date: Tuesday, August 04, 2015 Time: 7:00-10:00pm (after the NIWeek Block Diagram Party) Location: Scholz Garten, 1607 San Jacinto Blvd, Austin, TX 78701 (1 mile from Convention Center) Cost: $30 Early Bird (until July 17th) $35 Regular Admission (Until Aug 3rd) $40 At the door (Aug 4th) Meal Options: Standard meal is your choice of brisket, ribs, or chicken, with sides of beans, cole slaw, and potato salad. A vegetarian option is available to select during registration on the event page. Cash bar. Who: Everyone is welcome, including spouses traveling with you. Even if it’s your first time, expect to recognize many faces/names from the forums and NI R&D. What to wear: It’s an outdoor venue in Austin during August. So dress for the weather and comfort. Door Prizes: Towards the end of the event, we will have a raffle to give away prizes. All attendees are eligible and will receive a raffle ticket upon entry. Do you want to sponsor a door prize? - Continue Reading: If you or your company want to sponsor the LAVA 2015 BBQ door prize, please post a reply below. You can also include a small blurb about your company and a link to your website in the post below. By donating a prize you and your company will receive a small announcement of your choosing, during the event. We will ask you to write the announcement on a post-it note and will attach it to the prize to be read before awarding it. We would prefer a single item donation. If donating more than one item, then multiple identical items is preferred. If donating non-tangible items or something that is not physically with you. Then please bring a card with your contact info and instructions on how to collect the prize. This will be given to the winner. All prizes are acceptable except those listed below (examples from last year): Not recommended: Apparel (hats, t-shirts, underwear etc) Branded “trade show booth” type giveaways (mouse pads, pens, keychains etc) Software licenses (Toolkits, add-ons, Labview) Jokes or something meant as a gag and not a real prize. Hope to see you there! Chime in once you buy tickets to let everyone know you're coming.