Another third day of Windows printer crash testing and I've had some revelations and isolated five reproducible issues. I think # 1 (which I've never seen reported before) may be at the root of most of my problems.
A project is attached to each report that demonstrates all 5 bugs: (1) g.ClearRect in a printer object hangs Win32 apps on g.nextpage each time it is called. Calling ClearRect 100 times creates a small delay. By the time you call it a 5000 times during printing it hangs the computer for minutes. <http://support.realsoftware.com/feedback/viewreport.php?reportid=snrosdsd> (2) Calling g = OpenPrinter() twice locks up your computer <http://support.realsoftware.com/feedback/viewreport.php?reportid=qyhyssvn> (3) Assigning PrinterSetup.SetupString to a printersetup crashes when repeatedly assigned. It crashes every time after 65355 assignments. Interestingly, it doesn't crash when using the default p.setupstring. It always crashes when using the setupstring from the PageSetupDialog. <http://support.realsoftware.com/feedback/viewreport.php?reportid=vavrphab> (4) Drawing to a new graphics object crashes your app. Not directly related to printing but uncovered in my testing. <http://support.realsoftware.com/feedback/viewreport.php?reportid=onueoizk> (5) Repeatedly refreshing a counter in a Window will always crash Win32 Apps. This bug masked many loop tests. I saw this bug in several projects reporting other bugs in the feedback system. <http://support.realsoftware.com/feedback/viewreport.php?reportid=tnpvttvp> If you have any other printing issues, add them to the list and let's keep a complete list of the printing issues and bug IDs in front of REAL Software. Keith DeLong _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
