Jump to content

PaulG.

Members
  • Posts

    822
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by PaulG.

  1. QUOTE (hooovahh @ Mar 19 2009, 10:16 AM)

    Agreed, I think the quick answer to the question would be save it as a binary file (assuming you don't need it to be human readable) and the file size will be pretty smal.

    If this was a compression thread (which it didn't start as) I am also on the 7-zip bandwagon. I even tried making a API for LabVIEW but realized with my limited knowledge of DLL calls my only solution would be to use the command prompt to run the 7-zip command line utility. It would be a decent solution but would be operating system specific.

    Thread hijack. :ninja: Why would you want to mess around with command lines and a 3rd-party, open source (be afraid be very afraid) program when you can use native LV zip functions?

  2. QUOTE (vugie @ Mar 19 2009, 08:17 AM)

    For such a general question I would answer: 7-zip.

    Store your measurements in any way you like and automaticaly once a day or a week pack them to 7z by calling 7-zip command line executable.

    Yes, a zip file will probably be the smallest version of a data file you can have, but I would stick with native LV zip file functions.

  3. I was first sold on the project environment when I started setting up my DAQ channels under the project environment. I make a lot of executables paired up with DAQ systems for machines on the floor and need everything in one place. I created a lot of executables in 7.1 but since then I think its 10x easier doing so now out of a project.

  4. The next time you are scheduled for an interview, spend a couple of hours on the Internet and research the company you will be interviewing with. Find out what they are doing. Put yourself in that company and imagine what you could offer them. Think about that for a day or two. Then put yourself in the position of the manager you will be talking to. He/she will be asking: "why would I want to hire you?"

  5. I am using System Exec.VI to run .BAT files to program PICs. If I run the BAT file manually and the programmer is not plugged in or not connected or powered up (etc) I get a "No PICkit 2 found". I would really like to automate this step. How can I get this text to show up in one of my outputs from System Exec? Or do I have to do something else to get this message into my LV code?

    post-3786-1236776547.png?width=400

  6. QUOTE (Mark Yedinak @ Feb 10 2009, 11:04 AM)

    On a somewhat related topic do you know if it is possible for a subVI to inherit the background color of the calling VI? In my environment we reuse a large amount of our code and we have many general purpose VIs that are dialog boxes. Because we reuse our code I would like these dialog boxes to inherit the colors from the calling VI. The brute force method would be to get a reference to the calling VI and get it's color information and then set the colors for the subVI. This however may result in a flicker of the display (or we have to delay showing the FP until the colors are set). It would seem that an attribute allowing teh colors to be inherited would be convenient and useful. Is there such a thing?

    In your block diagram select a property node, link it to pane, then link that to the pane color. I think that's what you're looking for.

×
×
  • Create New...

Important Information

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