Re: [X2go-dev] Windows X2Go printing

2010-05-19 Thread Oleksandr Shneyder
John A. Sullivan III schrieb:
 On Tue, 2010-05-18 at 13:08 -0400, John A. Sullivan III wrote:
 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
 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.shney...@obviously-nice.de
web: www.obviously-nice.de

-- X2go - everywh...@home



signature.asc
Description: OpenPGP digital signature
___
X2go-dev mailing list
X2go-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


Re: [X2go-dev] Windows X2Go printing

2010-05-19 Thread John A. Sullivan III
On Wed, 2010-05-19 at 08:34 +0200, Oleksandr Shneyder wrote:
 John A. Sullivan III schrieb:
  On Tue, 2010-05-18 at 13:08 -0400, John A. Sullivan III wrote:
  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
  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
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

___
X2go-dev mailing list
X2go-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


[X2go-dev] Windows client crash ASSERT failure

2010-05-19 Thread John A. Sullivan III
Hello, all.  We installed the Trolltech Qt SDK for Windows and
downloaded the x2goclient-3.0.1-4 tarball from
x2go.obviously-nice.de/deb

Before attempting any changes, we simply built and ran the project.  It
crashed with:

ASSERT failure in QWidget: Widgets must be created in the GUI thread.,
file kernel/qwidget.cpp,line 1133
Invalid parameter passed to C runtime function

We tracked this down to initStatusDlg().  In line 7559, it calls
slotShowAdvancedStat().  On line 3966, it calls st.sync().  When it
calls QWinSettingsPrivate::sync() RegFlushKey(writeHandle()), it blows
up.

What have we done wrong? Thanks - John


___
X2go-dev mailing list
X2go-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev