Jump to content

crelf

Members
  • Content Count

    101
  • Joined

  • Last visited

Everything posted by crelf

  1. Hm - maybe it's something else. I just installed another package I'd created and got the same issue: and then I get a bunch of errors with my VIs, all related to the class abandoning its member VIs: I can send the package to you directly, but I can't attach it to a public forum.
  2. If I open the class (in user.lib\...) all of the VIs are gone. The folders (including accessor folders) are still there, and the class data is there (although blocked because the owning library has a "problem"), but no VIs.
  3. I built a package that includes a class and methods (the methods are available to the user on the palette), but when the user drops them on their block diagram, LabVIEW complains that the VI claims to be part of a library, but that library does not claim to own the VI.
  4. I have a typedef in a package (it's actually a member of the private data of a class). After the built package is installed, when I drop a VI that uses the class, LabVIEW goes off searching for the typedef control. The path it looks for the control in is: .\user.lib\package.llb\API\ControlName.ctl but it's actually here: .\user.lin\package.llb\NameSpacedControlName.ctl As you can see, both the path and name aren't as LabVIEW expects them. My guess is that classes that contain typedefls aren't updated when the typedef in namespaced.
  5. I created a test repository (didn't even put any packages in it), then quit VIPM. I deleted the files off the disk (the repo was in a folder on my desktop). Now I open the repo manager and it looks like it's managing the repo I'd deleted. I'd expect it to error out, or maybe tell me the repo's missing (and then allow me to browse for it, or remove it from the active repo list). I had to go into the VIPM options to find the repo listing and delete it manually from there.
  6. These answers are out of date, now that VIPM 2012 is out - yay! Now any Professional Edition users can create and maintain repositories.
  7. I installed LabVIEW 2011 (64bit), and installed some packages. I uninstalled LabVIEW 2011 (64bit) I installed LabVIEW 2011 (32bit), and installed some packages. I'm trying to remove a package from my library, but it's being reported as still installed in LabVIEW 2011 (64bit) and that I need to unistall it from there (I can't, because LabVIEW 2011 (64bit) isn't in the version drop-down anymore).
  8. It's not in my Tools menu either.
  9. Thanks Jim - that's exactly the answer I was expected, and hoping for.
  10. crelf

    Using xsd files

    Right, but have you found a way to apply an XML Schema check? ie: I'm using xsd schemas, not dtd. Cross posted to http://forums.ni.com/t5/LabVIEW/Validate-XML-to-xsd-schema/m-p/1952127#M648928
  11. crelf

    Using xsd files

    Hi Jim - can you elaborate on this? My experience is that EasyXML skips over items that aren't in the control definition and continues without error.
  12. Firstly, and I know I've said this before, but EasyXML is a great product that really fills a niche in the LabVIEW world. My customer wants a new version of a long-running application, and using EasyXML has saved me man-days of design, development and test time - so a big thanks to JKI! On to my quesiton: XML inherently doesn't support ordering of elements (that's why we can attached attributes to elements, so we can distinguish between them), but I was wondering if EasyXML does. From my limited testing, it looks like EasyXML will populate an array of elements in the order they appear in the XML file on disk - is this always the case? Here's a simple illustraive example - imagine this is deep inside an XML file: <GroupOfThings> <Thing ID="1"> <Size>Small</Size> <Colour>Red</Colour> </Thing> <Thing ID="2"> <Size>Medium</Size> <Colour>Green</Colour> </Thing> <Thing ID="3"> <Size>Large</Size> <Colour>Blue</Colour> </Thing> </GroupOfThings> Will the array in my XML cluster always have these elements in the order they appeared in the file? I know that it's not technically right to rely on this, but I'm hoping the answer is "yes"
  13. Sure - give me a shout when you've got a few minutes.
  14. Yes - you're right. That would completely solve the issue I'm having. In fact, I might want more than 2 vipb files - sometimes with only subsets of VIs, etc...
  15. So I would just need to remember to add the strip BDs post-build step for the separate release - hmmmm, I guess that would work, but I was hoping for something a little more automated...
  16. So I want to have 2 versions of my packages: one with (for use internally) and one without diagrams (for external release), and I wanted to get everyone's input before I tried anything, as the only things I can think of will require significant work to get up and running. Here are my two ideas: I could write a VI that takes a package, unzips it to a temporary location, removes BDs (using scripting), then zips everything back up into a new package. I could do the same as above, but make it a post-build step (so whenever I do a build, I'll get 2 packages output into separate folders) My biggest concern is the checksum that VIPM uses - if I try to use either of the two methods above, will my 2nd package be valid? PS: I thought about having two separate .vipm files, but that's not a good idea for 2 reasons: I can't control where the .vipm files go, so I'll be overwritting them all the time, and I *think* I want an external package for every internal package made, so I'd like that to be automated (don't want to have to manually build external packages - I just want them to be there when I need them).
  17. Meh - don't worry about it - I'm going up to 3.0.
  18. I just tried it again, and now it works. That makes me and at the same time.
  19. Nope - 2.0.3 (Build 1014). Another issue: after I tried the steps listed above, it emptied my VIPC.
  20. When I try to apply a VIPC, I get the following message: If I click "OK". then I get the following message: I have 2 questions: Most importantly, how do I fix this so I can apply the package configuration. Less importantly, why does my package configuration need to be saved? It's for a new version of a project that's in a regulated industry, and I need to justify why it changed. I've included the errors file - as you can tell, I tried it a few times: October_11_2009.txt
  21. Me too - we currently do this with a post-build hook, and it's a pain in the arse.
×
×
  • Create New...

Important Information

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