silence readonly messages

[Brian K. White]

On 8/25/2011 11:34 AM, Joe Chasan wrote:
> On Thu, Aug 25, 2011 at 10:40:04AM -0400, Craig Tooker wrote:

>> In the @entsel processing you must use waitkey to
>> manage *all* keyboard interaction.  When one one of the keys is entered
>> that you do not want to run with locking, issue a "goto @key(x)" instead
>> of a "pushkey (x);end".  The first method avoids locking the record
>> during the @key(x) routine (in fact it's not been triggered at all, it's
>> just running in @entsel because you used the "goto").  The second method
>> gives the keystroke back to filePro and then lets fP trigger the @key(x)
>> routine (and normal locking of the record).  You must end a non-locked
>> routine (one you used "goto" to enter) with a matching "goto @entsel"
>> instead of "end".

> i see what you are getting at and it probably would work, however this
> process table has 23 @key labels already and I think putting waitkey
> in @entsel is going to be a messy way of trying to get around it in
> this case.

Still it's a nice trick for the toolbox.

-- 
bkw