PFCLKBREAK also a no-op?

[Brian K. White]

----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at spamcop.net>
To: "Brian K. White" <brian at aljex.com>
Cc: <filepro-list at lists.celestial.com>
Sent: Friday, February 20, 2009 9:59 AM
Subject: Re: PFCLKBREAK also a no-op?


> Quoting Brian K. White (Fri, 20 Feb 2009 09:28:35 -0500):
> 
>> No matter what I set PFCLKBREAK to, unset, OLD, OFF,
>> in rclerk I can not avoid a break taking immediate effect.
> 
> What effect are you expecting to see?
> 
> [... snip code using INKEY ...]
> 
>> The only way I can see to do this now without PFCLKBREAK doing what
>> the manual claims, is do a "break off" just before I start looping
> 
> What do you think the manual claims that PFCLKBREAK=OLD does?
> 
> http://www.fptech.com/Products/Docs/FPFormat/envvars.shtml#PFCLKBREAK
> 
> [...]

You got me.

If I use ANY of these (at least, these are just what I tested):

inputpw
input popup
inputpw popup
msgbox
errorbox
popup  (ie: if screen not found, break out of error message)
popup update  (normal, screen exists with input fields)
waitkey

In all cases I detect @sk eq "BRKY" while still in @keyb

So I'm sorta not wrong for making the assumption that "input"
meant generally any form of input and not specifically
and exclusively the input statement.

However I do see the problem.

In all those cases above, the function waits for input.
Which means, I have pressed break
_while the function was waiting for input_
and so the function could intercept the break.

Inkey does not wait, which means, I'm almost never
actually IN an inkey statement. Once in a billion years
it might be possible for inkey to intercept a break, if I
happened to press it at exactly ridiculously the right time.

Where am I though during such a loop?
I started in @enstsel (which, @entsel I just checked, does
not intercept break the way all the above do)
@entsel read my "b" keypress to put me into @keyb,
but then, in terms of "what is reading my keystrokes right
now?" what is it?
Is it something that could intercept break under programmer
control like the other things above? Or would that break the
necessary "normal" function of breaking out of update mode
without saving?

-- 
Brian K. White      brian at aljex.com       http://profile.to/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!