John: Jeremy is suggesting what I have used. I have a similar but slightly different update of the data displayed in a listbox that needs to occur throughout the time it is in use. The Call Worker and Call Form is what I have used. It is easier to do than the type of code we used to have to write to do this kind of thing. It is also more efficient as it can run on a different core.
Jody > On Mar 8, 2020, at 12:38 PM, John J Foster via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi All, > > 4D v17 R5 (Mac and Windows single user standalone) > > I have a list box that needs to be built and available before the calculation > is complete. In this case I have some searches looking for particular > conditions and when found add them to the listbox. They could easily take a > few seconds to I’m guessing a minute or more. The searching could span 50-60 > sub searches within a 100 years of daily data (Think daily stock market data > but it’s not for the stock market). > > So I would like a strategy: > > - so that list box remains available as it’s being built. > > - the screen is not frozen as it’s being built. > > - The list box fills as each row is found/added and can be seen rebuilding. > > I’ve seen this kind of thing in a windows app (not 4D) and I’d like to > emulate the behavior. > > I need a strategy I’m guessing that involves another process which knows how > to communicate back to this form/listbox. Is this where workers could be > helpful? > > Does anyone have some snippets of code I could see to visualize the process? > > Appreciate, > John… > ********************************************************************** 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 **********************************************************************
