08-05-2010 03:50 PM
When using LabVIEW 2009's Print function to document some VIs, I notice that it cuts off some of Front Panel so that some of the labels and controls can not bee seen. This does not produce very good documentation.
Why does the Print function not show ALL of the Fron Panel of VIs?
How do I get the Print function to ALWAYS show the entire Front Panel?
08-05-2010 04:17 PM
What print function?
(print report? print subvVI at completion? print panel method? print manually from the file menu?)
08-05-2010 05:07 PM
Print from the File menu.
08-05-2010 05:50 PM
Please provide specifics. When you select File -> Print you are presented with dialog boxes. What are you choosing? For instance, are you printing to HTML? Printer? Does this happen with all VIs, or just specific ones?
08-05-2010 06:44 PM
OK. Steps to repeat:
PDF of result attached. Notice cut off at top. Labels and top of Plot missing.
I get the same result if I select other options or Print from File menu..
I get the same result if I use a real Printer or PDF driver substitute.
I get similar results with some other VIs.
Print Complete Front Panel should Print Complete Front Panel. Nothing should be cut off.
Not good documentation if important parts are missing and cut off.
Print function should make sure that all parts of Front Panel are printed with a little margin to spare.
08-05-2010 10:18 PM
I'm not seeing this issue. My printout does not appear cutoff.
08-06-2010 09:18 AM
I also do not see this behavior, and hence do not jump to the conclusion that the print function does not produce good documentation.
08-06-2010 09:48 AM
Look at the PDF I have attached. Clearly some important information is cutoff by the LabVIEW Print function..
Some of my VIs that I have tried printing have this problem with LabVIEW 2009, and some that I have tried do not. Clearly a problem exists with some VIs.
I am not going to try and run down by observation what attributes of a VI might cause information to be cutoff.
It is suffcient that I have more than one example that exhibits this behaior. A single example should be sufficient for a NI developer to determine the source of the problem within LabVIEW 2009.
Any time that documentation omits information critical to understanding the application, makes it BAD (IMHO) documentation.
08-06-2010 09:59 AM
We're not saying it didn't happen to you. We can see there is a problem in your .pdf. It's just that we haven't been able to duplicate it.
I tried to follow your steps exactly, but I don't know where you are getting PID_Loop.vi in step 2. Can you post that VI here? I went and grabbed a couple other PID vi's out of the example finder, but none of them gave me a problem.
08-06-2010 10:35 AM
I am not familiar with that VI is it a shipping example? Could you attach a simple VI that exhibits the problem for you?
A few things to check: