Re: VARPG Window API call - PrintDlgEx

The export is actually either PrintDlgExA or PrintDlgExW depending if you
are using ascii or Unicode.  The normal Win32 SDK in C/C++ will fix this up
for you at compile time via a #define.
Hope this helps.

Mike

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of qsrvbas@xxxxxxxxxxxx
Sent: Wednesday, March 28, 2007 10:28 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] VARPG Window API call - PrintDlgEx

wdsci-l-request@xxxxxxxxxxxx wrote:

   4. Re: VARPG Window API call - PrintDlgEx (Kurt Anderson)

Ok, having issues here.  First I was looking into PrintDlg, but realized
that for Windows 2000 (which is what we're on) I should be using
PrintDlgEx - http://msdn2.microsoft.com/en-us/library/ms646942.aspx

When I get to the print screen action, I get the following error: 0211
Error occurred while calling program or procedure PrintDlgEx.

Kurt:

At this point, I think your best choice is to ask on the 
ibm.software.varpg newsgroup on the news.software.ibm.com news 
server. I was right at my limit with the PrintWindow function. Going 
on actually to obtain the device context...?

Yeah, right. As if. <g>

When I was actively trying to do anything like what you're trying, I 
was using OS/2!

But if you find the right technique, I'd really love to hear about it.

Tom Liotta

My prototype:
      *  Display the Print Dialog Window
     D PrintDlgEx      PR            10u 0 ExtProc('PrintDlgEx')
     D                                     dll('comdlg32.dll')
     D                                     LinkAge(*StdCall)
     D  pPrintDS                       *   Value

My call (gresultUns = 10u 0):
  gResultUns = PrintDlgEx( pPrintDialogDS ); 

I've tried changing the case on ComDlg32.dll, but it doesn't seem to
matter.  I've verified that comdlg.dll is in C:\WinNT\System32, and that
directory is in my PATH.