Jump to content


  • Content Count

  • Joined

  • Days Won


ShaunR last won the day on December 2

ShaunR had the most liked content!

Community Reputation


About ShaunR

  • Rank
    LabVIEW Archetype

Profile Information

  • Gender

LabVIEW Information

  • Version
    LabVIEW 2009
  • Since

Recent Profile Visitors

16,987 profile views
  1. Looks like users are expecting it to solve their version control (or lack thereof) problems. I don't think NI should be entertaining that for a package builder.
  2. I saw a document about migrating from mscomctl to windows.forms (which is.NET). It mentioned the iTreeview and installing the VB runtime made available Microsoft Treeview in the Active X dialogue box.However. Trying to select it resulted in a dialogue saying it wasnt licenced. ¯\_(⁰͡ ͜ʖ⁰͡ )_/¯ Looks like you'll have to replace all the ActiveX containers with .NET containers.
  3. mscomctl is part of the Visual Basic run-time. You might try installing that IF iTreeview is actually part of it (are you sure it is?)
  4. It was probably registered as part of a 3rd party installer on the original platform. If you don't have that then you will need to find the activeX DLL (and it's dependencies) on the original machine, copy them over, and manually register it. Then keep your fingers and toes crossed.
  5. We can cope with that. In fact. We can cope with UTF 8 everywhere except the front panels. UTF8 LV80.vi
  6. NIPM is the odd one out. The rest are all zip files (including Github) but NIPM is multi-wrapped GZip and the zlib wwrapper we all use doesn't support it out of the box. I can already install all them (VIPM, GPM, raw zipped archives, Github, Sourceforge etc) except the NI one. But whilst looking at that I investigated SystemLink. That is the way forward, IMO - being able to manage addons, programs and installs from there and push them out if necessary (either from the cloud server or your local server). I'm very impressed with SystemLink and think it's an industry game-changer. About time too I never understood why they went for the JKI one in the first place. I moaned like hell when they first said that the JKI one was to be NIs preferred solution. So I guess they are only about 7 years late.
  7. Aren't all the addon installers (VIPM, GM and the one I was playing with) about to be made reduntant with the NI Installer now it supports addons?
  8. It's easy to be cavalier with other peoples privacy and security. If you haven't learnt from Facebook and the like, then I guess there's no point arguing.
  9. That looks like a binary problem. Send an email to the LVS-Tools support and show them this thread.
  10. Maybe it's your lack of imagination? It is at the intersection of IT. Cloud services are under the IT remit and new servers for each client aren't hard with VM instances. Talk to your IT and give them an instance template and they can spin up hundreds for you. Then just add links in your intranet pages. Of course if you really don't care about your clients data you can spin them up on Amazon Web Services or the Google Compute Engines.
  11. I think this is NI being responsible. Should you really be putting your customers' data on a 3rd party servers? If a customer is happy for that, then they can buy the service with full knowledge and give you access, but I don't think integrators, contractors or developers should be using it for their clients.
  12. I think I've come across something similar with named clusters and am not sure what the behaviour should be (but with events). The behaviour is difficult to describe but I'll have a go. I have this setup. I'm not sure how the name "Data" is chosen for the scaler type name, but it's the name of the event terminal on the VIM so that makes sense if you have to call it something. Deleting the Uint32 wire and wiring the cluster works sort of as expected with the ""Data" changing to "String" (i.e. one of the cluster elements). Popping up on the event data terminal reveals both cluster elements (String and UInt32). So far so good. Deleting the cluster wire and reattaching the Uint32 however doesn't change the event data terminal (remains as "String")and the VI is broken. BUT, popping up on the terminal shows the correct data type in the menu, which can be selected, and the VI is once again not broken. Note also that replacing the VIM yields the correct event data terminal type (called "Data"). OK. Not really a problem, but unexpected. So. Reattaching the cluster we get back to the second image (event data terminal is "String") as before. Now I change the cluster element name from "String" to "Value". But the event data terminal doesn't change, it remains as "String". The VI is not broken and popping up on it reveals the previous items "String" and "Uin32". The name change hasn't propagated nor can it be selected from the popup menu. It is recoverable, though although I'm not sure what would happen if I tried to generate the event with a string named "Value". Deleting the cluster wire and reattaching causes it to appear in the menu popup (broken VI with "String" as the event data terminal) so selecting it brings us back to a functioning VI. However. If instead of just deleting the wire, the VIM is replaced completely, then everything changes as I would expect (the "String" event data terminal changes to "Value" and the VI is unbroken with the correct popup menu entries). Arguably just a another example of "left handed scissors" but the cluster name selection and propagation strikes me as another manifestation of what drjdpowell is describing. srevent.vim
  • Create New...

Important Information

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