1. Printing
- Posted by Judith <camping at txcyber.com> Mar 01, 2002
- 493 views
The last time I used my printer with Win32lib was before (1) I installed Eu 2.3 and (2) I got a new printer with a USB port. Now when attempting to use getPrinter() routine from Win32lib I get a message with heading "Printer Err", a warning icon and message "An error occured during this operation" which doesn't appear to come from Win32lib so I assume it is from API PrintDlg. I get the error on both machines, one Win98 and the other XP. My version of comdlg32.dll is dated 1999 on Win98 and 8/18/2001 on the XP. I get the error whether I use the USB or Serial Cable with appropriate vendor software added. I get this error from Win32lib's Generic.exw so it is not related to my .exw program. I even traded back to the store the printer and got a different brand and still get the error. Anyone have an idea? Judith
2. Re: Printing
- Posted by Derek Parnell <ddparnell at bigpond.com> Mar 01, 2002
- 466 views
Do you get the error with any other software? Or just Euphoria? ----- Original Message ----- From: "Judith" <camping at txcyber.com> To: "EUforum" <EUforum at topica.com> Subject: Printing > > The last time I used my printer with Win32lib was before (1) I installed > Eu 2.3 and (2) I got a new printer with a USB port. > > Now when attempting to use getPrinter() routine from Win32lib I get a > message with heading "Printer Err", a warning icon and message "An error > occured during this operation" which doesn't appear to come from > Win32lib so I assume it is from API PrintDlg. I get the error on both > machines, one Win98 and the other XP. My version of comdlg32.dll is > dated 1999 on Win98 and 8/18/2001 on the XP. I get the error whether I > use the USB or Serial Cable with appropriate vendor software added. I > get this error from Win32lib's Generic.exw so it is not related to my > .exw program. I even traded back to the store the printer and got a > different brand and still get the error. > > Anyone have an idea? > > Judith > > > >
3. Re: Printing
- Posted by Derek Parnell <ddparnell at bigpond.com> Mar 01, 2002
- 439 views
----- Original Message ----- From: "Brian Broker" <bkb at cnw.com> To: "EUforum" <EUforum at topica.com> Subject: RE: Printing > > I can confirm your problem using a patched version of Eu version 2.2. I > never noticed because I don't print stuff using win32lib. > > I'll dig in and find out what's happening (I'm willing to bet it's > Win32lib...) > Me too Let me know if you find anything Brian.
4. Re: Printing
- Posted by Wolf <wolfritz at KING.IGS.NET> Mar 02, 2002
- 468 views
> xPrintDlg is returning 0 and CommDlgExtendedError is returning > PDERR_INITFAILURE. But only fails on patched version of interpretter. > I'll keep digging when I get a chance. Here's something that really confuses a newbie like me! -- Win32.hlp says: If you use the structure to initialize the dialog box controls, you must allocate space for and create the DEVMODE structure. (You should allocate a movable block of memory.) If you do not use the structure to initialize the dialog box controls, hDevMode may be NULL. In this case, PrintDlg allocates memory for the structure, initializes its members, and returns a handle that identifies it. -- I'm assuming that win32lib *is* trying to use the structure to initialize the dialog box, -- but DEVMODE isn't anywhere in sight ? i.e: store( mem, PRINTDLG_lStructSize, SIZEOF_PRINTDLG ) store( mem, PRINTDLG_nMinPage, 1 ) store( mem, PRINTDLG_flags, flags ) store( mem, PRINTDLG_nMaxPage, pMaxPages ) -- Perhaps the 3.10 version has an internal 'workaround' exception handler to 'baby' this, but the 4.0 version does not ? That " hDevMode *may* be NULL " is really explicit