[futurebasic] Re: [FB] Printing problem

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : April 2001 : Group Archive : Group : All Groups

From: "Parks, Eric K." <Parks@...>
Date: Tue, 24 Apr 2001 17:10:58 -0500
Al;
    I have a FN checkAbortKeys that checks for Cmd (.) and if Cmd(.) is
pressed it bypasses the whole ROUTE _toPrinter, ROUTE _toScreen printing
section and that certainly occurs before the print processing window comes
up (which takes a second or so). But the processing window always comes up
if you press OK in the Print Job window and if I do my Cmd (.) before it
comes up, it hangs. The printing is canceled in either case, except the
print processing window doesn't go away if I press Cmd (.) before it comes
up.
    I added a ON BREAK routine that just had CLOSE LPRINT and ROUTE
_toScreen in it, but it didn't help, so maybe it is a print driver problem.
I guess I will just have to type slower.
    Thanks for your help.
    
        Eric

>> on 4/24/01 4:07 PM, AlStaff@... at AlStaff@... wrote:

>> Before I route to the printer I opens a window to tell the user to press
>> Cmd (.) to stop the printing. After I press OK in the "Print Job" window, if
> I
>> press Cmd (.) _after_ my window opens and _after_ the Mac processing window
>> opens, everything works fine, the job is canceled and the processing window
>> goes away. However, if I press Cmd (.) after my window opens, but _before_
>> the Mac processing window opens (as I often do - my computer is slow),
>> the processing window gets stuck and doesn't go away. Can this be fixed?
> 
> 
> I have no idea if you tried any of this or if i'm even in the ballpark about
> what your problem is, but here are my suggestions.
> 
> 1. Is it possible to manually check if the user has the command and period
> keys pressed with some sort of checkKeys FN just before the print processing
> window opens? Or are you already doing that?
> 
> 2. Do you have an ON BREAK FN doBreak in your program? Try using that and
> checking if you're in your printing section and have the break FN close the
> printing and route to the window.
> 
> 3. If it happens after you no longer have control (the printer software takes
> over) then this could be a printer driver/software bug that you can't fix.
> 
> 
> Al Staffieri Jr.
> 
> AlStaff@...
> http://members.aol.com/AlStaff/index.html
> 
> --
> To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>
>