1. RE: exw.exe (when 4..0.0) and Win32lib
Yep. But it is not anything new to Win32lib that is causing this as I
have gone back through all the win32libs I have back to v50c and they
all get an error message when calling getPrinter function.
You can test this using the print menu option from Generic.exw in Demos
in the distribution.
--judith
Derek Parnell wrote:
> ----- 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
>
>
2. RE: exw.exe (when 4..0.0) and Win32lib
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.
Jonas
Judith Evans wrote:
> 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
>
>
3. RE: exw.exe (when 4..0.0) and Win32lib
- Posted by gertie at visionsix.com
Jan 30, 2003
On 30 Jan 2003, at 19:51, Jonas Temple 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?
Kat
4. RE: exw.exe (when 4..0.0) and Win32lib
Wolf,
Thanks for the "fix" for this! I applied to win32lib v57.9 and can now
print in bound programs.
Thanks!
Jonas
Wolf wrote:
> > 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>
>
>
