Well, I thought I was talking about workers in general, but that was under the assumption that all processes have some kind of execution cycle. Are you saying that a non-UI process (ex. pre-emptive thread) won’t have an execution cycle?
In either case, the only place I can think of where this might matter is in a worker process that has UI in it, so yes, CALL FORM is where the rubber meets the road here. I was trying to be more exact, but maybe assumed too much? -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <[email protected]> <www.synergyfarmsolutions.com> > On May 4, 2017, at 1:46 PM, Tim Nevels via 4D_Tech <[email protected]> > wrote: > > I think you are talking about using CALL FORM and not about workers in > general. In the past if you did CALL FORM 10 times to the same form, it would > do a redraw after each CALL FORM and thus could cause some flickering. Now > when a windows starts dealing with a CALL FORM it handles all the CALL FORMs > and then at the end it does a screen redraw. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
