Thanks for your reply. Sounds like I have just been incredibly lucky so far that print settings have not been messed up by a second process. I like to do the print settings at the start of a long print job so the user can start it and forget it - rather than have it stop when finally ready to print and wait for the user to intervene. Looks like I should re-think that idea.
Once I can get to v16, with its ability to change page orientation inside a print job, all should be well - unless there is going to be a problem with having more than 1 print job open at a time... Cheers, Keith > On 30/06/2017, at 2:38 pm, Keisuke Miyako wrote: > printing has always been a global operation. > > after all, it is the application that is doing printing, not the process. > > so if you OPEN PRINTING JOB in a process and hold (TRACE for example; just > close the progress window on Mac) > then call SET PRINT OPTION in a different process, > you get the error 1009 telling you can't do that once a printing job has > started. > > you might want to use a semaphore to make sure only one process prints at a > time. > >> 2017/06/30 8:01、Keith Goebel via 4D_Tech <[email protected] >> <mailto:[email protected]>> のメール: >> >> I have not tested it as experience has taught me that current behaviour can >> change if the docs say something and the actual behaviour is something else >> and the engineers decide to fix it - so I would prefer to clearly understand >> the docs and how to prevent a clash between processes. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************

