Hello, all. We are trying to finish off the punch list for our first major X2Go deployment so I expect to be sending lots of smaller issues to the list.
One not so small issue is a problem with using the X2Go client printing on Windows stations. The portability of this solution is magnificent but we are noticing that the windows client cannot directly print to the local printers. Whenever we send a print job from the X2Go server to the Windows X2Go client (3.0.1-4), the print dialog properly displays. However, no matter which local printer we choose, whichever application Windows has associated with PDF files opens instead and displays the PDF rather than printing it.
Has anyone else seen this behavior? It is 100% reproducible for us. Why is this happening? Is there a workaround? We're about to dive into the code to see what we can find but really don't know what we are looking at or for so any guidance would be greatly appreciated - John
Hello, all. We are trying to finish off the punch list for our first major X2Go deployment so I expect to be sending lots of smaller issues to the list.
One not so small issue is a problem with using the X2Go client printing on Windows stations. The portability of this solution is magnificent but we are noticing that the windows client cannot directly print to the local printers. Whenever we send a print job from the X2Go server to the Windows X2Go client (3.0.1-4), the print dialog properly displays. However, no matter which local printer we choose, whichever application Windows has associated with PDF files opens instead and displays the PDF rather than printing it.
Has anyone else seen this behavior? It is 100% reproducible for us. Why is this happening? Is there a workaround? We're about to dive into the code to see what we can find but really don't know what we are looking at or for so any guidance would be greatly appreciated - John <snip> Hmm . . . I'm noticing huge ifndef Q_OS_WIN sections eliminating almost all of the cupsprintersettingsdialog.cpp and cupsprint.cpp files. Am I beating my head against the wall trying to get the Windows client to use
On Tue, 2010-05-18 at 13:08 -0400, John A. Sullivan III wrote: the listed printers? As far as I can tell, one can't even access the printer settings no less print to them.
Does it print only to the PDF application by design? If so, why do we bother to display all the other printers? It is very misleading to the users. I would think there should only be a view as PDF option. Thanks
- John
John A. Sullivan III schrieb:
Hello, all. We are trying to finish off the punch list for our first major X2Go deployment so I expect to be sending lots of smaller issues to the list.
One not so small issue is a problem with using the X2Go client printing on Windows stations. The portability of this solution is magnificent but we are noticing that the windows client cannot directly print to the local printers. Whenever we send a print job from the X2Go server to the Windows X2Go client (3.0.1-4), the print dialog properly displays. However, no matter which local printer we choose, whichever application Windows has associated with PDF files opens instead and displays the PDF rather than printing it.
Has anyone else seen this behavior? It is 100% reproducible for us. Why is this happening? Is there a workaround? We're about to dive into the code to see what we can find but really don't know what we are looking at or for so any guidance would be greatly appreciated - John <snip> Hmm . . . I'm noticing huge ifndef Q_OS_WIN sections eliminating almost all of the cupsprintersettingsdialog.cpp and cupsprint.cpp files. Am I beating my head against the wall trying to get the Windows client to use
On Tue, 2010-05-18 at 13:08 -0400, John A. Sullivan III wrote: the listed printers? As far as I can tell, one can't even access the printer settings no less print to them.
Does it print only to the PDF application by design? If so, why do we bother to display all the other printers? It is very misleading to the users. I would think there should only be a view as PDF option. Thanks
- John
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hello John,
Windows Client have not support for CUPS, it using Win API function "ShellExecute" with parameters "print", printer name and PDF file. In this case Windows should send this file to application that associated with the file type "PDF". It is a task of specified application to print this file. On my windows testing machine Adobe Acrobat 5.0 doing this job well. However, after the document will be printed on specified printer Adobe Acrobat open this document in "view" mode.
You can also specify your own print command in printing dialog of x2goclient. For example, you can install Ghostprint and Ghostview and print using "gsprint.exe -query" -query - saying gsprint to show printers list
-- Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Hello, all. We are trying to finish off the punch list for our first major X2Go deployment so I expect to be sending lots of smaller issues to the list.
One not so small issue is a problem with using the X2Go client printing on Windows stations. The portability of this solution is magnificent but we are noticing that the windows client cannot directly print to the local printers. Whenever we send a print job from the X2Go server to the Windows X2Go client (3.0.1-4), the print dialog properly displays. However, no matter which local printer we choose, whichever application Windows has associated with PDF files opens instead and displays the PDF rather than printing it.
Has anyone else seen this behavior? It is 100% reproducible for us. Why is this happening? Is there a workaround? We're about to dive into the code to see what we can find but really don't know what we are looking at or for so any guidance would be greatly appreciated - John <snip> Hmm . . . I'm noticing huge ifndef Q_OS_WIN sections eliminating almost all of the cupsprintersettingsdialog.cpp and cupsprint.cpp files. Am I beating my head against the wall trying to get the Windows client to use
On Tue, 2010-05-18 at 13:08 -0400, John A. Sullivan III wrote: the listed printers? As far as I can tell, one can't even access the printer settings no less print to them.
Does it print only to the PDF application by design? If so, why do we bother to display all the other printers? It is very misleading to the users. I would think there should only be a view as PDF option. Thanks <snip> Windows Client have not support for CUPS, it using Win API function "ShellExecute" with parameters "print", printer name and PDF file. In
John A. Sullivan III schrieb: this case Windows should send this file to application that associated with the file type "PDF". It is a task of specified application to print this file. On my windows testing machine Adobe Acrobat 5.0 doing this job well. However, after the document will be printed on specified printer Adobe Acrobat open this document in "view" mode.
You can also specify your own print command in printing dialog of x2goclient. For example, you can install Ghostprint and Ghostview and print using "gsprint.exe -query" -query - saying gsprint to show printers list <snip> Thanks, Oleksandr. That saved me many, many hours. May I suggest that we remove the printer list from the view and offer the options to open in default PDF viewer and open with custom application? Showing the full
On Wed, 2010-05-19 at 08:34 +0200, Oleksandr Shneyder wrote: printer list gives the impression that one can print directly to the printers and is making our clients think there is a bug in X2Go rather than accepting that it is the way life is when using Windows - John
John A. Sullivan III schrieb:
Hello, all. We are trying to finish off the punch list for our first major X2Go deployment so I expect to be sending lots of smaller issues to the list.
One not so small issue is a problem with using the X2Go client printing on Windows stations. The portability of this solution is magnificent but we are noticing that the windows client cannot directly print to the local printers. Whenever we send a print job from the X2Go server to the Windows X2Go client (3.0.1-4), the print dialog properly displays. However, no matter which local printer we choose, whichever application Windows has associated with PDF files opens instead and displays the PDF rather than printing it.
Has anyone else seen this behavior? It is 100% reproducible for us. Why is this happening? Is there a workaround? We're about to dive into the code to see what we can find but really don't know what we are looking at or for so any guidance would be greatly appreciated - John <snip> Hmm . . . I'm noticing huge ifndef Q_OS_WIN sections eliminating almost all of the cupsprintersettingsdialog.cpp and cupsprint.cpp files. Am I beating my head against the wall trying to get the Windows client to use
On Tue, 2010-05-18 at 13:08 -0400, John A. Sullivan III wrote: the listed printers? As far as I can tell, one can't even access the printer settings no less print to them.
Does it print only to the PDF application by design? If so, why do we bother to display all the other printers? It is very misleading to the users. I would think there should only be a view as PDF option. Thanks <snip> Hello John,
Windows Client have not support for CUPS, it using Win API function "ShellExecute" with parameters "print", printer name and PDF file. In this case Windows should send this file to application that associated with the file type "PDF". It is a task of specified application to print this file. On my windows testing machine Adobe Acrobat 5.0 doing this job well. However, after the document will be printed on specified printer Adobe Acrobat open this document in "view" mode. <snip> Oops! I might have misunderstood what you said. Are you saying that, when you send the print job to the X2Go printer and choose a specific
On Wed, 2010-05-19 at 08:34 +0200, Oleksandr Shneyder wrote: printer in the X2Go client print dialog, that Acrobat opens but the job prints automatically and the only problem is that Acrobat remains open or are you saying Acrobat opens and then you must use the Acrobat print function manually to send the print job?
The latter is what we are seeing. Does wapi support the ShellExecuteEx call as opposed to ShellExecute? I'm pretty ignorant on this topic but, from what I read this morning, it looks like ShellExecuteEx does exit the called application when the requested action is completed. Thanks - John
John A. Sullivan III schrieb:
Hello, all. We are trying to finish off the punch list for our first major X2Go deployment so I expect to be sending lots of smaller issues to the list.
One not so small issue is a problem with using the X2Go client printing on Windows stations. The portability of this solution is magnificent but we are noticing that the windows client cannot directly print to the local printers. Whenever we send a print job from the X2Go server to the Windows X2Go client (3.0.1-4), the print dialog properly displays. However, no matter which local printer we choose, whichever application Windows has associated with PDF files opens instead and displays the PDF rather than printing it.
Has anyone else seen this behavior? It is 100% reproducible for us. Why is this happening? Is there a workaround? We're about to dive into the code to see what we can find but really don't know what we are looking at or for so any guidance would be greatly appreciated - John <snip> Hmm . . . I'm noticing huge ifndef Q_OS_WIN sections eliminating almost all of the cupsprintersettingsdialog.cpp and cupsprint.cpp files. Am I beating my head against the wall trying to get the Windows client to use
On Tue, 2010-05-18 at 13:08 -0400, John A. Sullivan III wrote: the listed printers? As far as I can tell, one can't even access the printer settings no less print to them.
Does it print only to the PDF application by design? If so, why do we bother to display all the other printers? It is very misleading to the users. I would think there should only be a view as PDF option. Thanks <snip> Hello John,
Windows Client have not support for CUPS, it using Win API function "ShellExecute" with parameters "print", printer name and PDF file. In this case Windows should send this file to application that associated with the file type "PDF". It is a task of specified application to print this file. On my windows testing machine Adobe Acrobat 5.0 doing this job well. However, after the document will be printed on specified printer Adobe Acrobat open this document in "view" mode. <snip> Oops! I might have misunderstood what you said. Are you saying that, when you send the print job to the X2Go printer and choose a specific
On Wed, 2010-05-19 at 08:34 +0200, Oleksandr Shneyder wrote: printer in the X2Go client print dialog, that Acrobat opens but the job prints automatically and the only problem is that Acrobat remains open or are you saying Acrobat opens and then you must use the Acrobat print function manually to send the print job?
The latter is what we are seeing. Does wapi support the ShellExecuteEx call as opposed to ShellExecute? I'm pretty ignorant on this topic but, from what I read this morning, it looks like ShellExecuteEx does exit the called application when the requested action is completed. Thanks - John <snip> Can anyone clarify from experience: When printing using the X2Go client
On Wed, 2010-05-19 at 10:37 -0400, John A. Sullivan III wrote: printing to print to local printers in Windows, does it open the pdf application AND automatically print the print job or does it simply open the pdf application? We are seeing the latter and want to confirm this is the expected behavior rather than something we mangled in the setup. Thanks - John
-
John A. Sullivan III -
Oleksandr Shneyder