Jump to content

Steamboat_Willie

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. The necessity to install the package ogrsc_dynamicpalette was key in my case. HOWEVER, it appears that the copy of that particular package, ogrsc_dynamicpalette-0.9-1.ogp that I found on that Sourceforge.net link is NOT the latest version. When I installed 0.9-1 the ONLY version of LabView that it allowed me to select to install was "7.1" (which I still keep installed on my PC) So I looked on my public PC and found that the version of that package was 0.19-1 Subsequently when deleting the older version and installing the NEWER version on my secure PC it DID provide me with an option to install as "2009" and then other packages installed without a hitch with the appropriate icons appearing on the LV block diagram functions "Add Ons" palette. Who maintains that Sourceforge.net listing of the OpenG toolkit files? Does anyone check it to see that the latest versions of the files are posted correctly? Copying over files one by one is cumbersome, but it works. (when done correctly and with up-to-date ogp files) (campers are happy again) Thanks. Ed
  2. I've re-opened LabView numerous times. I've also uninstalled and reinstalled the OpenG toolkit numerous times as well with the same unsuccessful results. It doesn't work. It's nowhere to be found on the functions palette. I am running LV 2009 but I do have other versions of LV installed on the machine as far back as 7. However on my public internet connected PC I also have numerous legacy versions of LabView installed and the OpenG toolkit installs and "activates" just fine there. I noticed that I have a total of 16 oglib_ files listed in the "Name" column along with the OpenG toolkit (version 1.0.0.5) name appearing at the bottom of that list. In front of each entry there is a red exclamation point appearing (on top of a LV icon). I've clicked on "Install Missing Dependencies" and it tells me that there is nothing to do and that all the packages are installed. And when I do a "Get Info" on all the openG listings they all indicate 2009. Could it be that when I downloaded all the files piecemeal from the sourceforge site that I missed something? Any suggestions? It would be nice to be able to use these utilities through the VIPM.
  3. That's great information. Thanks for taking the time to pass that along. However I still have the issue that the OpenG toolkit is still no where to be found on my functions palette and I see no menu choice anywhere to activate it. Installation reported "no erorrs" and all the pkg's are listed under repository as unpublished. Could you provide me with the method to activate all those OpenG toolkit packages now that installation was successful? Much appreciated. Ed
  4. That sourceforge link was perfect. I was able to down load, one by one, all of the OpenG toolkit package files and then copy them over to my private/secure PC. VI Package Manager was quickly able to load and install everything. However in the VIPM column labeled "Repository" it says "UNPUBLISHED" and within my LV block diagram on my controls palette under "Add Ons" it is blank. (When I tried installing the OpenG toolkit on a PC that was connected to the internet, that's where the OpenG functions icon appears.) So what needs to be done in order to activate or publish these packages now that they've been successfully installed on this private/secure PC? I think I'm close, almost got it fixed. Thanks. Ed
  5. I would think that a user who is developing LabView applications in an environment where internet access is restricted for, legitimate reasons, (I'm not at liberty to provide more details here) would not be placed at a disadvantage just because there is no internet connectivity. I could see if one's interest in "upgrading" to a "professional" edition would be to utilize and enjoy additional benefits that an upgrade to a product yields. That's fine. But requiring an upgrade just to be able to use the product in the same manner that community edition users already do in the "internet connected" world does not make for an even playing field. I have no need to develop custom VIP packages and configurations. NI already demonstrated to me that a ".vip" file is ALL I would need to solve my problem. Seems quite simple. And what would be the downside in posting a .vip file along with each VI package that is released and available to the open community? An internet-connected user installs a new package by method "A" and the non-connected user by method "B". Simple. Easy. Done. And, certainly more happy VIPM campers. I'd like to see the VIPM development team rethink this policy and provide users in the predicament that I'm in with the ability to merely access a .vip file. I'm sure the development team could work something out here. Thanks. Ed
  6. Usage of the VIPM is new territory for me. I have 2 PC's in my development environment. PC "A" is connected to the internet. PC "B" is NOT as it is on a dedicated private secure network and due to constraints connection to the "public" (outside world) internet is not allowed. I downloaded the VIPM installation file onto my "public" PC and was able to successfully install it on my "private" PC by first copying the installation file over via an external CD. The problem I have is that I can't seem to figure out how to download a VI package "file" itself with the intention of NOT installing it because of the separation between the "public" and "private" networks I'm faced with. All my LabView development work is done on the private network. When I posed my dilemma to the NI support desk when I wanted to obtain their VI scripting package, they provided me with an ftp link to the ".vip" file for that package. Thus I was able to download "only" (but not install) a VI package. That scripting pkg was subsequently copied via an external CD over to the private network machine and successfully installed. Is there a way to do this and access the actual VIP files with the assorted openG VI packages I see that are available ? Looks like lots of neat utilities and time savers (stuff I'd like to "not be living without"). If my ultimate target machine was and could be connected to the public internet then, obviously, I wouldn't have this problem. FAQ's clearly explain how to "install" VIP's but only through usage of the VIPM app itself. Hope I've explained myself correctly. Thanks. Ed
×
×
  • Create New...

Important Information

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