Jump to content

Michael Aivaliotis

Administrators
  • Content Count

    6,047
  • Joined

  • Last visited

  • Days Won

    68

Everything posted by Michael Aivaliotis

  1. I'm sure if you request that from JKI, they could help. But last I recall VIPM typically installs the installer in: C:\ProgramData\JKI\VI Package Manager 20xx\updates\VIPM This might have changed, but try there. Also, if the setup isn't there, look for the vipm-update.aiu file in that area. It's a text file that includes a URL to the installer. PS: I don't work at JKI.
  2. So basically, if someone forgot to wire the error out. Gotcha.
  3. Thanks for the report. Can others reproduce this? Want to know if it's browser specific or associated with some other behavior.
  4. If you don't already have a systematic way to manage errors in your code and are relying on automatic error handling exclusively, then that's a problem. Automatic error handling has some limited usefulness early on in development perhaps, to detect areas of your code that are not plugged into your current error handling system. However you shouldn't depend on it exclusively for handling errors.
  5. The icon has a question mark but it's bold and solid. Not grey and dimmed. Missing VIs or nodes show up dimmed.
  6. Don't use the NI LabVIEW installer. Use the installer distributed from JKI. Uninstall VIPM then install it form JKI. Never use the NI installer for VIPM.
  7. Do people still use ini files? I mean XML, Json? What is the consensus. Should any effort be put into this? Yes, the MGI tool is way faster. Yes, I'm derailing this post...
  8. I was already subscribed and looked at what my podcast player (Apple podcasts) was using as the URL. So ya, I cheated.
  9. Well technically, an event frame is for user events. If you programmatically resize the panel (which is not a user action), then it's your job to tell everyone to fix themselves. Sure we could argue forever on that one point. But it seems much less hacky to send a panel resize cleanup message than to jiggle the splitters. Imagine someone trying to read your code and figure out why you're jiggling the splitters.
  10. Try this: https://anchor.fm/s/71f9ee0/podcast/rss Also, if you go to the podcast homepage on Anchor, click on the button that says: Listen in your favorite app.
  11. I assume you already have a mechanism to send messages to these sub-paneled VIs? Could you use that?
  12. Ya, that's strange. I tested it on chrome and safari and it looks fine for me. I notice the dots are working and the discussion round icon is dimmed. So it seems it's partially working, but not the bolding? What browser? Chrome?
  13. The scrollbar is behaving as it should. I suggest you create property nodes for the scrollbar and investigate the help on those. When you create a brand new scrollbar it sets the DocMax and DocMin to 10 and 0 respectively. It uses that as a reference if you don't set them yourself. So when the data fed to the scrollbar exceeds 10 then LabVIEW automatically adjusts the scrollbar slider width to handle the visualization of the larger data. LabVIEW also takes into consideration the actual width of the scrollbar as well. So if you stretch it out then the slider will resize larger accordingly. If you wanted to make the slider wider, then you need to set the PageSize property to be a certain fraction of DocMax. Since the default is probably 1, which will make the slider super-thin.
  14. Hmm, I'm not seeing this message myself. Try logging out and back in to see if it goes away.
  15. Which notification? Do you mean the "Something went wrong" message? So I think you are mentioning 2 issues. One is the message and the other is the incomplete profile step.
  16. How do you login? Using built-in login or facebook? I'm thinking it's a caching issue maybe.
  17. Wow, those LAVA cats really worked overtime. Looks like the site is back up and working. Let me know if you notice anything strange. Thanks for your patience! I just noticed we now hav a leaderboard. Cool.
  18. If that's real, please add it to OpenGDS, like now!
  19. Automatic error handling is for noobs.
  20. I get that. But thinking about it even more. It seems you would want to have a feature to completely remove an installed Package ?. Otherwise you would have an ever-expanding database of files.
  21. Hey LAVAmaniacs! It's been a while since I poked at the LAVA server. There seems to be a lot cobwebs and dust in the server room. The LAVA software hasn't been updated in a couple years. That's way too long. I'm going to jump in and see what I can do about upgrading the LAVA back-end to the latest and greatest. This will fix many issues. Last time I tried this, it failed and I had to revert back. I didn't plan on it failing and didn't allocate time for getting tech support from Invision. This time I'm planning for the upgrade to fail and then getting Invision support involved. This means the site might be offline for a few days beyond the weekend. Sorry, but it's a small pain we have to go through for long-term stability and security. Don't worry though. This time I have a crack team to help me out:
  22. Well, the idea behind the original LabVIEW Wiki was to create a Wikipedia for LabVIEW. So linking to external content was welcome, using similar rules as Wikipedia uses. Mainly as cross-reference material or at the bottom of a page where further research could be done. Having said that. A page with all the LabVIEW blogs (which we had before) would definitely be ok. However, creating a dedicated sales page, for example, for your new Modbus toolkit would be forbidden. But a page dedicated to how Modbus works and used in LabVIEW is fine. Where then you could create a section on that page linking to all the Modbus toolkits and code available. There's a fine line that needs to be walked. The Wiki needs too have a definite purpose. It's ok if that purpose changes. But if it's just left wide open, then it will serve no purpose and be just another dumping ground on the web.
  23. So if LabVIEW is not trying to manipulate the linked files (delete, rename, etc) and is just reading or saving them, then symbolic link should be enough. However if LabVIEW tries try to manage these files then it's better to go with hard links. In this context I mean the LabVIEW IDE, not the package manager written in LabVIEW. But I think the two link types might not matter to the package manager written in LabVIEW. Since it will always be working with the installed files in the Application Data folder. All of the "work" on the files would be done there and not under the LabVIEW IDE folders. Some work to unzip the files and some other work to create the links which would be a bunch of Admin-level command line calls. Am I understanding this right? @rolfk As far as the zip changes your making. Explain the use-case of supporting "hard" or "soft" links in the first place. How do you use this in the context of zip?
×
×
  • Create New...

Important Information

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