1. More Printing woes
- Posted by Greg Haberek <g.haberek at comcast.net> Apr 03, 2003
- 331 views
Ok... after determining HOW to print, WHERE to print, and WHAT to print, now I can't Print! grrr... woe is me. I downloaded the newest Win32Lib (0.58.03) per suggestion of Derek, since getPageSetup() crashed. but what's worse is now it does nothing! neither does getPrinter()! Why?
2. Re: More Printing woes
- Posted by Derek Parnell <ddparnell at bigpond.com> Apr 03, 2003
- 328 views
Greg, I've made a mistake in the include file "tk_mem.e". In the routine "myAllocate", find the line ... mem_set( lAddr, lMemSize, 0) and change it to ... mem_set( lAddr, 0, lMemSize) This error was caused by me not remembering the correct order of parameters and not checking the manual either. I changed this routine recently to get around a shortcoming in Euphoria 2.4 that deals with Windows memory allocation. Sorry for the inconvenience. ---------------- cheers, Derek Parnell ----- Original Message ----- From: "Greg Haberek" <g.haberek at comcast.net> To: "EUforum" <EUforum at topica.com> Sent: Friday, April 04, 2003 7:08 AM Subject: More Printing woes > > Ok... after determining HOW to print, WHERE to print, and WHAT to print, now I can't Print! > grrr... woe is me. I downloaded the newest Win32Lib (0.58.03) per suggestion of Derek, since > getPageSetup() crashed. but what's worse is now it does nothing! neither does getPrinter()! Why? > > > > TOPICA - Start your own email discussion group. FREE! >
3. Re: More Printing woes
- Posted by Derek Parnell <ddparnell at bigpond.com> Apr 04, 2003
- 321 views
On Thu, 3 Apr 2003 23:15:42 +0000, Brian Broker <bkb at cnw.com> wrote: > > Derek, > > This is how it looks now: > > function myAllocate(integer pSize) > atom lAddr > atom lPreSize integer lMemSize > > lAddr = allocate(pSize) > mem_set(lAddr, pSize, 0) > return lAddr > > -- old junk snipped -- > > end function > > > You are saying it could/should look like this? > > function myAllocate(integer pSize) > atom lAddr > > lAddr = allocate(pSize) > mem_set(lAddr, 0, pSize) > return lAddr > end function > > -- Brian > Thanks mate, of course, I've got v0.58.4 on my machine, haven't I - duhh! The 0.58.3 version has a simplistic fix in it. v0.58.4 has a lot more protection built-in. Sorry got the confusion. -- cheers, Derek Parnell
4. Re: More Printing woes
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> Apr 04, 2003
- 335 views
On Thu, 3 Apr 2003 21:44:39 +0000, Jonas Temple <jtemple at yhti.net> wrote: >This fix was supplied a while back that might help: > >In the routine getPrintChoice() comment out the line: > >store( mem, PRINTDLG_nMinPage, 1 ) > >and then later in this routine, comment out: > >store( mem, PRINTDLG_nMaxPage, pMaxPages ) > Just for the record, I have strong suspicions about that. My investigations indicated that if you pass a sequence of flags in pFlags, you must include PD_RETURNDC otherwise it won't work, at all.=20 Either add that flag or or_all() the sequence before passing it. (Appropriate changes were included in my recent post to Derek four days ago, updates to getPrintChoice, to automatically include PD_RETURNDC if it is not present). Greg, are you passing a sequence of flags as the second parameter to getPrintCoice? If so, can you try both approaches and let me know, thanks. If you want I can post you my modified 0.58.2 win32lib for testing. >I don't know if these changes are in the win32lib you downloaded. I checked, they are not in 0.58.3. Pete