> -----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 > >
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. We are porting our apps to RB from an environment where the users are used to each report defaulting to the printer setup they used the last time they ran that particular report. Moreover, we allow them to give a meaningful name to each saved printer setup and select them from a dropdown list. MUCH easier than going through the dialog every time. Real Software must fix this problem if they expect to attract serious Windows developers. I would even be happy if they opened up a mechanism for the program to setup the printer, eg., margins and orientation. I think the Windows API allows for this. Tim Hare Telios Systems Company _______________________________________________ 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>
