How does one set printer variables so they stick?

 

I can print switchlists with the variables set to "letter" sized paper and "tumble", but I cannot see where to make these choices stick.

 

Probably in a config file somewhere, but neither the Help Pages nor my bumbling around have uncovered it.

 

Cheers,

/ Bruce /

 

I will be following this because I, too, have long wished that OperationsPro would at least honor the printer preferences I have set in Windows.

 

As it is, every time I print a manifest or switchlist (or anything else I want double-sided), I have to manually intervene because otherwise, it will ignore the double-sided default setting of the printer and print it single-sided. (I should note that everything else I print from that computer honors the double-sided default.)

 

I opened a bug report about this long ago (in SourceForge!), but it was diluted/sidetracked when another user added his similar, but different issue to mine. ISTR his was resolved in some manner, but my original issue faded into oblivion and was eventually closed.

 

Steve

"Breezlys"

On Sat, Dec 28, 2024 at 03:54 PM, Breezlys wrote:

I will be following this because I, too, have long wished that OperationsPro would at least honor the printer preferences I have set in Windows.

Steve,

 

The issue is that JMRI is using old print routines that were heavy modified to allow print preview.  What we need is a developer with a lot of time on their hands to upgrade the print routines and recode the print preview.  A lot of coding and testing that I personally don't want to venture into.

 

I think the best workaround is to print to PDF and then the printing of the PDF will honor the printer preferences.

 

Dan

On Sun, Dec 29, 2024 at 07:29 AM, Dan Boudreau wrote:

On Sat, Dec 28, 2024 at 03:54 PM, Breezlys wrote:

I will be following this because I, too, have long wished that OperationsPro would at least honor the printer preferences I have set in Windows.

Steve,

 

The issue is that JMRI is using old print routines that were heavy modified to allow print preview.  What we need is a developer with a lot of time on their hands to upgrade the print routines and recode the print preview.  A lot of coding and testing that I personally don't want to venture into.

 

I think the best workaround is to print to PDF and then the printing of the PDF will honor the printer preferences.

 

Dan

 

Dan,

 

 Thanks for explaining the "why" behind the issue. I unfortunately have zero coding experience, so I am of no help and will stop complaining :-)

 

Thanks also for the suggestion to print to PDF. However, in my case, that is actually more involved than manually changing the double-sided preference when the dialog appears. I will keep that thought in my back pocket, though, in case it's ever needed.

 

I appreciate all you do to make OperationsPro such a great program. Happy Holidays!

 

Steve

"Breezlys"

On Sun, Dec 29, 2024 at 10:35 AM, Breezlys wrote:

Thanks for explaining the "why" behind the issue. I unfortunately have zero coding experience, so I am of no help and will stop complaining :-)

What he said. Thanks for the info.

 

Where does one file a bug report? I wasn't aware that such a system existed.

 

Cheers,

/ Bruce /

 

Phil G

I agree with Dan.  Save stuff as a .pdf.

 

I am still developing my JMRI OperationsPro skills for our club, so make sure all our trains "work" by repeatedly building the train and saving each Build Report and Manifest as a .pdf, until I can see that each train runs properly.  I give these docs a file name such as TF03 Coal MTs - HSPG-EW 10-21 build 2 manifest.pdf.

 

This tells me that this is the Tuesday/Friday train #03 Coal MTs from HSPG to EW staging built 10-21, build attempt 2, the Manifest.  I've had to "build" some trains as many as 9 times to get them to build and run properly, so it's good practice to keep a copy of each build.

 

Then because we run a "sequence" of trains each session, once a train runs successfully in OpsPro, I save the Manifest as a .pdf, then print two copies for the ops session:  one for the train Operator, the 2nd "just in case".

 

Yeah, it's tedious, but proved invaluable when trying to figure out why trains didn't build.  

 

I have an ingrained habit, formed long ago while working, of saving and filing documents as .pdf files.  It's a matter of personal preference.  And if I don't use a previous file version for several days, weeks or months, it eventually gets deleted.

 

It's just how I roll!

 

Happy and Healthy New Year to everyone!

 

CRZ