David......
The crash can happen even if you do not save the setup string to a
file and read it back in. It can also happen if you just reuse the
same setup string over and over.... but not as often with 2006 as
with previous versions.
I reported what I think could be a related problem..... see:
http://www.realsoftware.com/feedback/viewreport.php?reportid=sinfamxk
Somehow the setup string gets corrupted such that passing to an
OpenPrinterDialog(ps) will no longer open the dialog..... it just
returns nil.... but I cannot seem to get anyone at RS to look at
this problem.
Jim
On Apr 10, 2006, at 6:48 PM, realbasic-nug-
[EMAIL PROTECTED] wrote:
Message: 8
Subject: Re: Windows HP printing update?
From: David Miller <[EMAIL PROTECTED]>
Date: Mon, 10 Apr 2006 16:09:54 -0400
I have something to add here.
I've been going through my app, trying to work around the same
issue (crash)
when trying to put a string into a newly created printerSetup
object, and
I've tried everything I've seen in any of these threads and suggested
workarounds.
(Allocating the printerSetup only once; putting a delay, between
allocation
and actually doing something with it; various pieces of code to
compare
the string inside the printerSetup after it's been put in there, to
make
sure it matches the source string, such as doing an md5 comparison).
None of this -completely- solves the problem for all users. It can
lessen the frequency, and sometimes a crash will happen only once on
startup, but the issue of this happening still crops up too
frequently.
_______________________________________________
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>
