--- Clay Leeds <[EMAIL PROTECTED]> wrote:It would be great if there were a flag/arg that
could be added to the COMMAND LINE to enable some type of identification
to be appended (like the date/time stamp like '200310061500' might be
good--or since it's a flag/arg, append the filename if the flag is
present)
I currently don't see too much need for that--that information has only the life of a few seconds to a few minutes while waiting in a printer queue. For the time/date, look in the second column if you're viewing a Windows print queue... ;-)
Glen
First let me say, that this new addition will be helpful. I agree that we probably don't need to add a date/time stamp per se.
I thought I'd give a little background on why I made this request in the first place.
While it's true that the print job only has the life of a few seconds when sent to my trusty local HP 1200, if I send it to get RIP'd on our networked printer (which is defaulted to save jobs in queue for a week, in case someone wants to re-print a document), I ended up with a bajillion "Java Printing" documents. Thankfully, the main impetus of resolving this nagging problem (allow viewers of the queue a better idea of what's been/being printed) is resolved by changing it to "FOP Document". The RIP'er has an EFI Fiery-based Java applet which displays the job queue. I can 'click' one of "Java Printing" jobs and then re-print it or do whatever I want. The date & time columns would certainly suffice for identification purposes.
Thanks again for all of your collective (not to mention quick!) help on this.
Web Maestro Clay
