Browse Lookups

[Bruce Easton]

"Events are a much better methodology [than timers]"

Agreed.  I work almost exclusively with browser-based projects anymore, 
so  I had to test this:

If:  @sk EQ "DTAB"

to be sure that you can't trap the PageDown as a browse-lookup trigger.


On 6/26/18 1:45 PM, Paul McNary via Filepro-list wrote:
> I like the idea of callbacks in filePro! :-)
>
>
> On 6/26/2018 11:17 AM, Fairlight via Filepro-list wrote:
>> On Tue, Jun 26, 2018 at 11:38:36AM -0400, Richard Kreiss via 
>> Filepro-list thus spoke:
>>> I would love to be able to set a timer for a browse which would 
>>> execute a
>>> sub-routine.
>> You're thinking very old-school.
>>
>> What would be better than a timer is a set of configurable callbacks 
>> which
>> execute processing table segments upon various events.
>>
>> * Begin lookup
>> * Changed record
>> * End of matches
>> * Close lookup
>>
>> In this fashion, you can configure what you like, without having to rely
>> on an arbitrary timer which may be smaller than desirable, or larger 
>> than
>> necessary (thus wasting time).  Timers generally suck, to put it 
>> bluntly.
>> They're often too crude a tool.  Events are a much better methodology 
>> for
>> this sort of functionality.
>>
>> And lo and behold, filePro already supports events in general terms.  So
>> why not have @brsbeg, @brsrcd, @brsend, and @brscls as system-based 
>> events
>> which function like conventional callbacks?
>>
>> m->
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus