The problem is not limited to HP printers/driver..... I have seen it
lots of times on my Epson C84.....
It also has been reported on both InkJet and Laser.....
Jim
On Apr 10, 2006, at 6:48 PM, realbasic-nug-
[EMAIL PROTECTED] wrote:
Message: 12
Subject: Re: Windows HP printing update
From: David Miller <[EMAIL PROTECTED]>
Date: Mon, 10 Apr 2006 16:18:51 -0400
No, that is not an acceptable solution.
Printing is a fundamental capability of the language, and if something
is broken (and in this case, it is and has been for an extended
period of
time), it needs to be fixed.
It's not as if we, the developers, aren't making a conscious effort
to pin
this down and help solve the problem. The bug reports listed have
detail,
and I know of at least one local system with an HP connected that I
can
consistently get my application to crash on.
Here's another hint:
The HP is a clue; in all, or nearly all of the cases which report
crashes,
it happens only with an HP connected; there are never any reports
of this
from Epson or Canon users; and also, on a system with an HP
connected, I can
work around the problem by having a user switch to -any other-
printer in the
list (so that the saved setupString in prefs is non-HP). Next time
they
launch: no crash. Then they can do Page Setup in my app; switch to
the HP;
the printerSetup doesn't choke and become unstable on the string;
printing to
the HP works; as long as they switch away from the HP before they
quit, they'll
be OK the next time they launch.
David Miller
Senior Software Developer, Digital Color Solutions
ColorVision
_______________________________________________
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>
