Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/09/2019 in all areas

  1. It was not developed in a bubble. There was already a close relationship between the VIPM team and NI. So they knew the requirements and the need. It's been over 5 years since the release of NIPM, so not much movement however... That might have been the first step, but hardly the long-term plan. In reality, I think the main reason for lack of development on NIPM is that people got shuffled around and new management came in and the original development plans for NIPM got put on a shelf. I can tell you that NI had the goal of full VIPM replacement. There is much churn internally at NI on where to take NIPM next. They are back to wanting to add features to facilitate better reuse library installation for current LabVIEW (how to achieve this is not clear). For sure however, this is the clear case with NXG. I suggest you watch this video:
    1 point
  2. NI caused this problem themselves. NIPM should have provided all the features of VIPM from the start and then added GPM features. Lack of investment. Now they're playing catchup, but technology is moving on.
    1 point
  3. Sorry, my examples posted earlier were in 8.5.1. Here they are back saved to 8.0. Bruce Create Shortcut.vi Set Shortcut Properties.vi
    1 point
  4. I use these VIs. They're from a bunch of Windows utility VIs that I have. Bruce Create Shortcut.vi Set Shortcut Properties.vi
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.