on 4/25/01 11:46 AM, Chris Stasny at staz@... wrote:

> snip...
>> 
>>>> I pulled all of that and used only a ON LPRINT function that
>>>> contained only the statments
>>>> 
>>>> call getkeys (keys)
>>>> if keys.row2& = _cmdPeriod then close LPRINT
>>> 
>>> 
>>> So where is the place where you send the PRERROR?
>>> 
>>> 
>>>> 
>>>> but the problem remains. It works correctly only if I press Cmd (.) after
>>>> the processing window comes up.  A bug in the print driver seems more
>>>> attractive as time goes on. Thanks for everyones help.
>>>> 
>>>> Eric
>>>> 
>>>> --
>> 
>> I don't understand the question.  I guess I am confused (not uncommon). I
>> thought that CLOSE LPRINT (responding to Cmd (.)) should shut down the
>> printing and get rid of the processing window, which happens when  Cmd (.)
>> is pressed after the processing window is open. Also adding ROUTE _toScreen
>> after the above two statements doesn't fix the problem.
>> 
>> Eric
>> 
>> --
> 
> 
> Since I can't duplicate this, I have to guess about what is going on.
> My guess is that FB is in the midst of setting up the printer when
> you shut it down. Therefore CLOSE LPRINT cannot sent a PRERROR and
> you can. It is only one line of code. It won't hurt for you to try
> it. No one else can try it because no one else has your set up.

I put CALL PRSETERROR in the function as shown below (is that correct?). I
also have an ON LPRINT doCheckPrinting line in the main and no ON BREAK
statement. No change. It prints fine if no Cmd (.) is pressed. It aborts
printing if Cmd (.) is pressed before or after the processing window is
opened, but hangs if I type Cmd (.) before it opens.  It works the same with
and without the CLOSE LPRINT line. NOTE - IT NEVER BEEPS!??

    Eric


local
dim keys as keyMap
local fn doCheckPrinting

BEEP
call getkeys (keys)
long if keys.row2& = _cmdPeriod
   CALL PrSetError(_iPRabort)
close LPRINT

end if

end fn