Just discovered this ugly issue in RB 5.5: My app prints a 20 pages
report, which takes some seconds. If I press ESC while the print
progress dialog is visible, it crashes hard.
Debugger doesn't catch anything, OS X reports a hard crash.
Does someone know, if this is a bug? Might this be fixed in 2K5?
If it is, I suppose it is related to a no longer available
framebuffer/graphics context to be printed in, because
OS X reports a problem deep in a core lib/framework.
I hope, that I can catch this some way, but even an exception handler
in the main printing methods doesn't catch anything. If this is a bug,
I had to notify all my customers....
_______________________________________________
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>
|