1. exw.exe (when 4..0.0) and Win32lib
Hi All,
Now I remember why I used exw.exe as 3.1 for so long; exw.exe as 4.0 and
Win32lib will not allow printing from my exw program. Although I can
bind it (I guess my bind.exe is still 3.1) and print ok. This has me a
bit worried if RDS is going to issue Eu 2.4 with exw.exe as 4.0. and
bind.exe as 4.0 also. I like the effect of Windows as 4.0 but certainly
don't want to be converting back and forth for those applications that
need to print data.
If I recall correctly there was some discussion on Topica about this
quite awhile ago but when doing a search on messages I can't locate if
there was any solution with Win32lib. Does anyone remember this?
--judith
2. Re: exw.exe (when 4..0.0) and Win32lib
----- Original Message -----
From: "Judith Evans" <camping at txcyber.com>
To: "EUforum" <EUforum at topica.com>
Subject: exw.exe (when 4..0.0) and Win32lib
>
> Hi All,
>
> Now I remember why I used exw.exe as 3.1 for so long; exw.exe as 4.0 and
> Win32lib will not allow printing from my exw program. Although I can
> bind it (I guess my bind.exe is still 3.1) and print ok. This has me a
> bit worried if RDS is going to issue Eu 2.4 with exw.exe as 4.0. and
> bind.exe as 4.0 also. I like the effect of Windows as 4.0 but certainly
> don't want to be converting back and forth for those applications that
> need to print data.
>
> If I recall correctly there was some discussion on Topica about this
> quite awhile ago but when doing a search on messages I can't locate if
> there was any solution with Win32lib. Does anyone remember this?
> --judith
>
>
>
> TOPICA - Start your own email discussion group. FREE!
I don't recall this being discussed, Judith. Are you saying that if exw.exe
is a 4.0 program then win32lib programs fail to print?
----------------
cheers,
Derek Parnell
3. Re: exw.exe (when 4..0.0) and Win32lib
> I don't recall this being discussed, Judith. Are you saying that if exw.exe
> is a 4.0 program then win32lib programs fail to print?
Yes, and CommDlgExtendedError() only returns PDERR_INITFAILURE , which is, well,
useless...
Can get around this temporarily by calling getPrintChoice() directly, using
PD_RETURNDEFAULT as second parameter, but
then there's *no* dialog, just a print to default, assuming one's set up.
GetPageSetup() still works, but, it's not the same dialog.
4. Re: exw.exe (when 4..0.0) and Win32lib
> Now I remember why I used exw.exe as 3.1 for so long; exw.exe as 4.0 and
> Win32lib will not allow printing from my exw program.
Here's a <snipped> fix out of getPrintChoice(), that works on my simple
'prints'.
This prints *everything*,
however you can still select the printer, and it's properties.
... amused by the fact that pMaxPages seems to be 0 based 
Wolf
<snip>
mem=acquire_mem(0,SIZEOF_PRINTDLG)
store(mem,PRINTDLG_lStructSize,SIZEOF_PRINTDLG)
--store(mem,PRINTDLG_nMinPage,1) --always killed dialog!
else
mem=pPrintDlg
end if
if sequence(pFlags)then
flags=or_all(pFlags)
else
flags=or_all({pFlags,PD_PAGENUMS,PD_RETURNDC})
end if
store(mem,PRINTDLG_flags,flags)
--** added this
store(mem,PRINTDLG_nCopies,1)
-- this is irrelevent anyways, unless you know the number of pages ahead?
--store(mem,PRINTDLG_nMaxPage,pMaxPages)
releasePrinter()
<end-snip>
5. Re: exw.exe (when 4..0.0) and Win32lib
Kat wrote:
> > I wanted to confirm this as I just ran across this as well. I get a
> > message box that says "An error occured during this operation" when
> > attempting to print from a bound program using 4.0. The program works
> > fine when running interpreted.
>
> I was sorta wondering how changing the version would work too, since win3.x-
> is cooperative multitasked, and win95+ is preemptive multitasked. If nothing
> else, won't benchmarks between Eu and other languages be throw off?
I don't think so. It seems that with 3.1 in PE header, Windows only emulates
some 3.1 differences, but the application otherwise runs as a normal 32 bit
program. And multitasking does not have that big impact on benchmarks as they
are
run on light system load.
Martin
