> On Sep 14, 2016, at 10:44 AM, Cannon Smith <[email protected]> > wrote: > > All the other environments I know of use one thread for all the UI and other > threads as needed for background or potentially long running tasks. This is > akin to putting all our windows in the Application process and using > preemptive processes for background tasks. If I heard right, Thomas alluded > to this as an idea if you had the chance to start an app from scratch.
It is a terrible limitation and one of the reasons I stopped using some other development tools. For example, if a process wants to get a user confirmation it must call the main process to show the dialog. Then the dialog has to make *callbacks* back to the process to continue (CALL WORKER?, CALL FORM?). Things that can be handled very simply in 4D a few lines of conditional statements turn in to multiple procedures having to deal with interprocess communication. John DeSoi, Ph.D. ********************************************************************** 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] **********************************************************************
