I say yes. At the very least, progress indicators really REALLY need concurrency, if for nothing else than the animation. Plus, concurrency can be used to *queue* complex time consuming operations with databases and such. Data grids for example could queue up “pages” of data in the background without having to intercept the data grid routines that load the data into the DG. So as a user scrolls through the data, the data grid could “page ahead” (or behind) instead of load all the data at once, or else have code that loads each page as the user scrolls.
I could think of a few other things off the top of my head, but yes. Bob S On Mar 7, 2015, at 09:37 , Richard Gaskin <[email protected]<mailto:[email protected]>> wrote: Is concurrency something we want to pursue for LiveCode? _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
