> Le 8 févr. 2019 à 17:48, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > [...] Is there a way to trap use actions like that so I can block the > On timer code from running?
Each new SET TIMER "kills" the previously set one, so it allows to postpone or cancel next 'On timer'. For example when the user types into a search box, send the query after he has stopped input since one or 2 seconds. Maybe something like this in form method could work: jobPostponed:=60*2 //2 seconds, for example case of on keystroke set timer(jobPostponed) on timer set timer(0) job.do(please) set timer(jobPostponed) end case Thinking after, there is surely more events to consider (On click, double clic, menu, etc.) -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************