Jump to content

todd

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Reuse package source for my (very small) group goes in c:\reuse\<package name>\ Each package folder has its own scc repository and associated bug/feature tracking and wiki. Post-build package options are set to lock VIs, CTLs, lvlibs, lvclass, ... That way, when packaged code gets used in a project and someone tries to debug into it, they quickly realize they're in a package, not in their source anymore. If the package is complex enough that you need to edit it often, leave it unlocked during development. Change it in c:\reuse\..., build, install, debug from the project that calls the packaged code, repeat until it's robust. If the package source changes every day, it's not really a package, yet.
  2. These links may or may not be helpful: http://forums.ni.com/t5/LabVIEW/labview-for-linux-Ubuntu-64-bit/td-p/1106325 http://forums.ni.com/t5/LabVIEW/Labview-8-installation-on-Ubuntu-libdb-so-2/m-p/404847?requireLogin=False
  3. Another way, described here: http://lavag.org/topic/16974-put-a-decoration-on-a-controls-palette/?p=104270 Place a class control on a front panel. Save that VI. Add the VI to the Controls palette. When browsing for the VI to add, change the file pattern to *.*
  4. I don't understand why you would want three copies of the same VI, with different namespace. Why not: 1) Package up a low-level package (one that doesn't call any other VIs that will get packaged). 1a) If those VIs happen to be in an lvlib, just rename the lvlib file, not its contents - for easier re-linking. 2a) Check one of the apps out of source control 2b) Link the pre-packaged VIs to the ones in the package 2c) Check in the app and the vipc file
  5. Follow-up: I removed the text files from the libraries. Those files still exist in the build - they just aren't members of the lvlibs, anymore.
  6. I'm packaging an lvlib that includes a text file. The text file ends up in the correct folder alongside the VIs, but the path shown in the lvlib xml is the pre-build path. How do I fix this? <?xml version='1.0' encoding='UTF-8'?> <Library LVVersion="12008004"> <Property Name="NI.Lib.Icon" Type="Bin">removed</Property> <Property Name="NI.Lib.SourceVersion" Type="Int">302022660</Property> <Property Name="NI.Lib.Version" Type="Str">1.0.0.0</Property> <Property Name="NI.LV.All.SourceOnly" Type="Bool">false</Property> <Item Name="libName" Type="Folder"> <Item Name="dirName" Type="Folder"> <Item Name="About libName.txt" Type="Document" URL="../../../../../../../../../../../../../lv/dev/projDir/.productDir/libName/dirName/About libName.txt"/> <Item Name="company_lib_one.vi" Type="VI" URL="..//company_lib_one.vi"/> <Item Name="company_lib_two.vi" Type="VI" URL="..//company_lib_two.vi"/> </Item>
  7. No errors when I run it, here. Questions about OpenG libraries are probably best asked here: http://lavag.org/forum/45-openg/ http://lavag.org/topic/14056-openg-discussions-moving-to-lava/
  8. The workaround is to write the type-defd cluster into the private data (which I leave non-type-defd) of a class dedicated to that use. NI suggested trying LabVIEW 2012 - haven't had a chance to try that, yet.
  9. I have a reusable library for serial devices (I know, who doesn't?) that is being converted to the Actor Framework (yes, there is a good reason). This one has a "<company>_Transport.lvlib:Create.vi". The descriptor is a type-def cluster of: Transport Type enum, VISA resource name, ... and three children of "Actor Framework.lvlib:Message.lvclass". After building the package, when I place Create.vi, the cluster wire is void. It doesn't matter if I use a non-type-defd cluster, or if the parent Message.lvclass is used instead of the children. If I wire the classes in separately (not in a cluster), everything is fine - but the next package on the list has a lot more messages to include. Any advice is welcome. Cross-posted to AF community: https://decibel.ni.com/content/thread/15047
  10. Well, running as Administrator makes it work. My account has admin priviledges, but I see that doesn't matter. Thanks!
  11. I'm not sure this is a VIPM issue, but I'm hoping someone has an idea what's going on. I'm running 2011.0.1 Community build 1692, LV2010 32, and LV 2011 32 on win7 64. VIPM dialog windows are empty and I can't close them with the X - only with Task Manager. LV dialog windows in my own LV apps are ok. Any ideas?
×
×
  • Create New...

Important Information

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