Jump to content

JKSH

Members
  • Posts

    494
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by JKSH

  1. Hi, See http://zone.ni.com/reference/en-XX/help/371361K-01/glang/setting_permissions/ You set the permissions to 200 (decimal) = 110 010 000 (binary). Try setting it to 110 110 110 (binary) = 438 (decimal) to give everyone read/write permissions? (If that doesn't work, you need to find out how Windows Server manages file permissions)
  2. Hi, I clicked on your first link but it says "It appears you're not allowed to view what you requested", even though I joined the group.
  3. Thanks for your answers, everyone! Creating a VI based on an existing template and then replacing placeholder components was a clean and easy way to do things. I haven't installed the GDS; I believe it will be part of LabVIEW 2014? Anyway, thanks for the lead. I'm sure there's lots of gems to be found inside when I need to dig deeper.
  4. Thanks for the lead, Yair! I had a quick look, and it seems to be exactly the kind of example that I need. I'll dig through it when I have time.
  5. Hi, If I'm not mistaken, Vision Common Resources provides the ability to run those VIs in a deployed environment, while the IMAQdx drivers provides the ability to develop code using those VIs. Have you installed IMAQdx drivers?
  6. Hi all, I'm trying to programmatically create and modify LVClasses. So far, I've managed to do the following via LabVIEW scripting: Create a new LVClass Save the new LVClass to disk Make one LVClass a subclass of another Create property definition folders My next step is to create class methods (static dispatch for now), but I'm stuck. I can't figure out how to add an LVClass control/indicator to a VI. I tried the following, but LabVIEW complained, "Type mismatch: Object cannot be cast to the specific type". I can't find any other LVClass-related items in the list. I tried to figure out what I should pass to New VI Object.vi, by querying an existing static dispatch VI as follows: Apparently, the FP elements I want are called "LabVIEWClassControl", and they have a ClassID of 102. However, "LabVIEWClassControl". isn't available in the list. When I wired 102 into New VI Object.vi, I was told "The specified object was not found." How do I programmatically drop an LVClass control/indicator into a VI? More fundamentally, how do I script a new static dispatch VI? Thanks in advance!
  7. Thanks, rolfk! I tested your fix with Michael's test cases (with "ignore duplicate delimiters?" both TRUE and FALSE) -- they all produce the correct results. Do you know when this will make it into the VIPM? I'd rather not fork, to avoid fragmentation. Do you know if there's a way for non-members to submit patches?
  8. A bit late to the discussion, but I'd like to add: I use comments to document the assumptions made when writing a section of code. As a piece of software grows (or if code is copied into another project), some earlier assumptions may need to be revised.
  9. A kind soul at ni.com as built the executable; all is well http://forums.ni.com/t5/LabVIEW/built-it-for-me/m-p/2469268 weld3li, good luck for your project. I'm just curious; how come your supervisor wants you to build an .exe if he/she knows it's hard to get Application Builder in your country?
  10. I just posted a long-ish comment on a status update. It was apparently too long, but LAVA didn't give me any warning -- it just posted a truncated version of it. A warning would be much appreciated.
  11. So, is the bug being tracked now? Is this forum the place to report them?
  12. Whoops, thanks for the info about Line Feed. Looks like the bug was between the keyboard and the chair.
  13. Hi all, I first filed some bug reports at SourceForge, before realizing that the bug tracker there has been quiet for a year. Is this the preferred place to file reports? Anyway, the two bugs are: String to 1D Array output is empty, if delimiter not found String to 1D Array doesn't recognize End of Line Constant
×
×
  • Create New...

Important Information

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