Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: Controls Guy on January 07, 2015, 10:31:30 PM
-
Even if I check "Black and White", ladder prints in the colors as shown on screen. (Win 7, DMD 1.3.1, CutePDF print driver)
-
I don't use CutePDF print driver but check you print driver settings.
I use doPDF and have no problems printing in B&W.
-
Hmmm. I could not duplicate it on my Win7 w/1.3.1, although I am using a different .PDF printer driver. B&W came out B&W. Normal came out w/colors for my Nicknames, Extra Info, and Description text in my Ladder print out.
FYI, the "black and white" setting is done by Designer. It basically saves off the current color scheme, grabs the "Monochrome" color setup (this is hard coded set of colors inside Designer) during the print, then restores the saved off colors.
Do Print Preview with that driver and B&W checked, and see if you get B&W on your screen. If that is working correctly, but the actual .PDF output is not, there's something weird going on.
You might try deleting your DmPrint.rst file from your Designer1_3\Bin folder, just to see if that fixes it.
-
Here's a summary of what I found when I tried it this morning.
If I do File/Print, ladder previews and prints in B&W.
If I do File/Print All with only ladder code blocks checked, no docs or Xref, ladder previews in B&W, but prints to PDF in color.
I didn't try deleting that file yet. When I do, I'll let you know the results.
Thanks!
-
Here's a summary of what I found when I tried it this morning.
If I do File/Print, ladder previews and prints in B&W.
If I do File/Print All with only ladder code blocks checked, no docs or Xref, ladder previews in B&W, but prints to PDF in color.
I didn't try deleting that file yet. When I do, I'll let you know the results.
Thanks!
Duplicated it via Print All. We will look at it.
What I got was the first code-block was B&W, but subsequent code-blocks were in color. Should be an easy fix.
-
Yup, same here. I thought it applied to all the ladder, but the first routine printed is a very short $TopOfScan routine that has very little in it, so when reading the printout, after the cover sheet I almost unconsciously skip that one and start reading with the next, which is $Main (which printed in color).
BTW, what determines the order in which the code blocks are printed? Execution order?
-
BTW, what determines the order in which the code blocks are printed? Execution order?
I don't have the code in front of me, but I believe the order is
1. non-"main" scan code-blocks
2. "main" scan code-blocks in execution order
So code-blocks like $tFirstScan and $tLastScan, then in a future version, Interrupt Service Routines, Functions, and Subroutines, all fall into the non-"main" scan code-blocks. Then the print-out order is execution order (regardless of "frequency" or system vs. user). That way the print-out page flow follows exactly the order of execution, just like rungs within a code-block.
Looking at the order of the code-blocks in the Print-All dialog's Items to Print tree, it is exactly as I stated above (see attached screen shot).