Michael Aivaliotis

It's the workflow I use and it works for me. If I'm juggling 523 projects then perhaps my workflow would be different. I currently have about 10 active projects but maybe 3-4 hot ones. Lots of hard drive space and most of it SSDs. So it's fine. As far as test VMs, you just need one for each OS. It's a judgement call. Perhaps you have one VM that you use for several projects that use the same LV version and reuse libraries - who knows. How do you handle different NI hardware driver versions that come out every 6 months? We can agree that LabVIEW sucks in this regard. No news there. Using VMs is "Putting the cart before the horse". Sure, but I'm done with creating large scale infrastructure tools to fix some other company's inactivity. Some folks younger than me with more energy to spare can do that - I'm good. I'd rather spend the development effort on my customers, which gives me greater reward and returns. Both emotionally and financially. Don't get me wrong. I still build tools and reuse libraries. But most likely not a VIPM-type of tool or add-on.

The logo got wiped during the upgrade. I still have it. I just need to put it back. Just waiting for things to settle down a bit. I'm really liking the new layout and feel of it. It seems more user friendly and mobile responsive.

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: