Sorry for the cross post, but I believe this issue is relevant to
both lists, and I'd really like to know what people think...
Out of curiosity, has anyone ever explored any options with REAL to
directly fund a fix to this printing issue? I know they have the
option on their website to join their developer program and receive
"QuickFix" priority bug fixes, which are defined as:
" At the beginning of each release cycle of REALbasic, the technical
staff and management of REAL Software determine which new features
and bug fixes should be addressed in the next release of the product.
As a general policy, features and fixes are chosen with the intent to
provide the greatest amount of benefit to the largest number of users
for the lowest development cost.
Occasionally, a customer identifies a critical fix that does not meet
this threshold in spite of being very important to their development
efforts. It is for these customers that REAL Software offers
"QuickFix" Priority Bug Fixes.
By applying a QuickFix, a REALbasic customer can escalate a bug to
top priority. The bug will be reviewed by the REAL Software Testing
and Engineering staff and if it meets the characteristics of a
QuickFix (i.e., it can fixed within one day or less) it will be moved
to the top of the bug fixing list and resolved quickly in a future
alpha or beta release."
I am not well enough informed to speak to whether or not this
printing problem would fall into the "Quick Fix" category, but I
suspect that it would not because it will likely take > 1 day to fix it.
So, I'd just like to find out if anyone has approached REAL to find
out if they offer any other options - could we as a community raise
the funds necessary to force development of a fix for this bug?
Thoughts?
-- Kimball Larsen
President and Head Developer, Incredicode, Inc.
On May 11, 2006, at 9:20 AM, Keith DeLong wrote:
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Keith
DeLong
Sent: Wednesday, May 10, 2006 4:46 PM
To: REALbasic NUG
Subject: Re: Printing Crashes In Windows Explained - WORKAROUND!
I think the minor inconvenience of confirming the printer,
orientation and
margins -- if needed -- once per program run is more than an
acceptable
workaround until REAL can fix assigning to .setupstring.
Does anyone see a problem or fatal flaw with this workaround in
their apps?
Keith DeLong
Tim,
Yes. It is a MAJOR inconvenience in our apps, where each report is a
separate program that collects info from the user (date range,
customer
range, sort order, etc.) and then prints and exits. It means they
have to
walk through the stupid dialogs every single time they run the
report. This
is simply not acceptable.
Not true -- you only need to show a printer dialog only once per
application
run. See my prior email to Rog on this thread.
I admit it's less than perfect to not be able to store printer
settings
between application runs. However, for two years this has been a
growing
issue for my business. Since I now have in excess of 50,000 users
printing
from my software regularly, the ability to restore sanity -- not
having my
app randomly crashing, people legitimately complaining, support
sosts going
through the roof, software refunds and lost good will -- it it a
work around
I can live with until REAL fixes the setupstring method.
BTW, yesterday was the first time in two years I've been able to
reliably
narrow the problem down replicate and explain all the variety of
results of
the crashes on this bug. It is absolutely shameful (and indicative
of a
serious management problem) that they didn't care enough about the
seriousness of this bug and their developers to make it a priority and
figure it out themselves or at least cooperate with their
developers crying
for years to get this addressed...
At least today I have a little hope REAL will fix the problem now that
someone has told them where exactly it exists.
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>
