Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darren

  1. Perhaps not, since the functionality of that VI is accomplished with a VI that is already in the LabVIEW shipping palettes (see my previous response): -D
  2. Yes, the "VI Documentation" VIs (including Append Front Panel and Append Control Image) are available with the standard Report Generation VIs that come with LabVIEW. As for generating a report with images and text, you can use the HTML report type to generate an HTML file that contains your report. There is currently no way to generate .rtf files with the Report Generation VIs without Microsoft Word. -D
  3. I posted an answer to this topic on info.labview as well. You can use the Append Front Panel Image to Report.vi from the Report Generation palette to accomplish this same behavior. And if there are only certain control images you want to include in the report, you can use Append Control Image to Report.vi. As for the problems loading this VI on a machine without the Report Generation Toolkit installed, I'm looking into ways to fix that in future versions of LabVIEW and the toolkit. -D
  4. In LabVIEW 8.0, I included a VI at vi.lib\Utility\MD5Checksum.llb\MD5Checksum file.vi that will do the MD5 checksum of a file. The implementation is 100% G, so it will work on all platforms. I haven't benchmarked it against other MD5 methods, but it's there if you need it. -D
  5. I can't reproduce it in 8.0. Is there anything peculiar (VISA I/O refnums, matrix datatype, etc.) in the code you are turning into a subVI? -D
  6. The problem is occurring because you are not initializing the shift register that is wired to the offset input of the Hexadecimal String to Number function in your For Loop. Whatever index value was the last value written to that shift register will be the first value given the next time the VI runs. So this will probably be a large offset value that is at the end of the file, thus resulting in no hexadecimal value found, thus resulting in a default value (zero) being output from the function. I think if you wire a zero constant to initialize the shift register the problem will be solved.
  7. Hi John, I don't think there is any way to change the color of the sweep line on a sweep chart. Assuming no one else presents a way to do it, can you submit this as a product suggestion on the NI website? http://digital.ni.com/applications/psc.nsf/default Thanks, -D
  8. LabVIEW R&D is aware of this frustration regarding right-click options on functions. We are planning on addressing this issue in a future LabVIEW version. Thanks for the feedback...just wanted to let y'all know that we're listening... -D
  9. Sorry, was I supposed to wait a while for people to be shocked and amazed before answering? -D
  10. It is possible to have a 0xn or an nx0 array in LabVIEW, where n is a non-zero number. It has to do with the way the dimension data is stored. The easiest way I know to reproduce this is to take three empty 1D arrays, wire them all into a Build Array, and the size of the resulting 2D array is 3x0. If any of the dimensions of an array are zero, you have an empty array. In LabVIEW 7.x and previous, the best way to determine if an array is empty is to do an Array Size, and wire the resulting array of dimensions to Multiply Array Elements to see if you get zero. In LabVIEW 8.0 and later, you
  11. Hi Dave, I knew you weren't upset...I figured if I gave you as much information as possible, we could keep it that way. This toolkit did not have an official Release Notes document, by the way, so any list of bug fixes would come through me. Like I said, they're all minor...glancing over the list, it appears I fixed several minor ActiveX issues and we ironed out a few installer issues as well. -D
  12. Hi Dave, Sorry you had to go through all this hassle...I thought the problem was only with the Upgrade Advisor, but apparently our ISRs are quoting the incorrect price as well. I have contacted the proper authorities to get this addressed as soon as possible. -D P.S. - In addition to the two major issues I previously mentioned, there are also several minor bug fixes in RGT 1.1.1 that I threw in there because I had time. Let me know if you'd like more information on those.
  13. Hi Dave, There were two main fixes in the 1.1.1 update...the first, as you mentioned, is the palette incompatibilities between RGT 1.1 and LabVIEW 8.0. The second issue is the fact that the MS Office Report Express VI from RGT 1.1 did not work properly in LabVIEW 8.0. Just the other day I noticed that the Upgrade Advisor was not properly "advising" regarding an upgrade from 1.1 to 1.1.1. This should be a free upgrade. The $195 price should be for users upgrading from 1.0.x to 1.1.1. I have already talked to our web team about getting the Upgrade Advisor fixed to reflect the $0 cost tha
  14. Here's a VI that should work for you. It's saved in LabVIEW 7.0 format. -D Download File:post-4441-1146000771.vi
  15. I believe if you put two '\r\n' characters before and after a given sentence/paragraph, that will cause the paragraph to word wrap. You can try it in your VI by going to Description and Tip and pressing Enter twice before your paragraph, and after your paragraph. I have attached a VI that contains your Numeric control with the context help wrapping appropriately after making this change. If you are changing the description programatically, just convert single \r\n characters into \r\n\r\n. I noticed in your control's context help you just have \n characters, so if you're updating the conte
  16. Search the LabVIEW Help for "Report Generation". You should find a topic on the Report Generation VIs, which help you generate Standard (for your printer) and HTML reports. You can purchase the Report Generation Toolkit if you want to expand the ability of these VIs to generate Excel and Word reports as well. -D
  17. I can confirm that this does happen on my machine in LabVIEW 7.1. It appears to be fixed in 8.0. -D
  18. Is it a game show any of us have heard of before? -D
  19. Uh oh, Ben mentioned Nazis. I am officially invoking Godwin's Law and declaring this debate over. Since Ben was arguing that the April Fool's joke was not funny, it is officially deemed funny. Oh, and all of us Big Brothers over in LabVIEW R&D think Michael's April Fool's joke was hilarious... -D
  20. To my knowledge, there is no way to control the width/spacing of a listbox tip strip, and there is no way to show a tip strip for hidden string control text. I haven't written any XControls yet, so I don't know if this is something you could implement with an XControl. -D
  21. Aww, no fair! You edited your post so that my reply wasn't applicable anymore... Nothing to read here, carry on, carry on... -D
  22. I'm Rowlf the Dog...I'm guessing because for the entertainment question I said that I would play the piano. -D
  23. Sorry guys...even from my days in the AE department long, long ago, it was drilled into our heads never to talk about potential release dates for unreleased software. No points off for trying, though... -D
  24. Ok, I just found out that there is currently no way to turn off the tip strips for listbox cells where the column width does not accomodate the cell text. I guess your best workaround would be to make sure the text in the cell does not go past the width of the column. -D
  25. The tip strip is being displayed on the listbox because the text in the cell is wider than the column width. That is why you don't see the tip strip with a smaller string like "abc". Also, the previous suggestion of using the "Show FP Tip Strips" property will not work in this case...that property only deals with the "Tip" that you can set on a control or indicator by right-clicking and choosing "Description and Tip". For now, a workaround for you could be to resize the column width to make it wide enough to display the entire cell string. I will investigate to see if there is any way to h
  • Create New...

Important Information

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