learn something new everyday

[Fairlight]

That's because save acts as an end, same as screen does.  Any end
condition precludes the trigger, as you've just ended before you've
actually triggered the callback.  You never actually -left- the field.
You saved whilst still in that field.

Working as intended and historically expected, near as I can tell.  And
I don't often say that concerning fP.

m->


On Wed, Jun 02, 2021 at 03:24:13PM -0500, Richard D. Williams via Filepro-list thus spoke:
> I just discovered a disturbing thing.
> If you use @whp* or @wuk* and have @wlf processing for the field you're in,
> the @wlf processing does not execute!
> 
> I am working on a system that use F8 and F10 for SAVE and EXIT respectively.
> If I am trying to control a user to make sure the data they have entered is
> correct and they press F8 to SAVE, it never executes the @wlf for that
> field.
> The program executes an ESCAPE at the @wuk and goes directly to the top of
> the input table.
> Would I need to capture the field number they were in when the F8 was
> pressed?
> 
> I guess programming would have to be created to validate all fields values
> after the ESCAPE.
> 
> Does anyone else have issues with this?
> 
> Richard D. Williams
> 
> 
> 
> -- 
> This email has been checked for viruses by AVG.
> https://www.avg.com
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Audio panton, cogito singularis.