Hi Peter, > Method specified in CALL FORM is called in the form just like form method, > but is not part of form method, nor is it called from form method.
Yes that was my problem expecting that it was somehow related to the form method, per se. After I finish the main search routine I’ll get to work on implementing this. Appreciate, John… > On Mar 9, 2020, at 10:27 AM, Peter Bozek <peter.bo...@gmail.com> wrote: > > > > On Mon, Mar 9, 2020 at 6:22 PM John J Foster via 4D_Tech > <4d_tech@lists.4d.com <mailto:4d_tech@lists.4d.com>> wrote: > > Ref: "An easier way to think of CALL FORM is to look at it as the old ON > OUTSIDE CALL event in a form, but with the added bonus of being able pass > data to the form as parameters from the calling process, without using global > variables." > > I kind of get that but can’t see where the form captures as event (we don't > have On Call Form) so I know where to append to the listbox with the new > rows/data as it’s being returned. > > It does not. Method specified in CALL FORM is called in the form just like > form method, but is not part of form method, nor is it called from form > method. > > pB > > > Does that make sense? That’s where my confusion lies. > > John… > > > > > On Mar 9, 2020, at 9:42 AM, John J Foster <trueg...@isomedia.com > > <mailto:trueg...@isomedia.com>> wrote: > > > > Hi Peter, > > > > Yea, that’s what I thought! > > > > So trying to understand (aka, visualize in my minds eye before I code) how > > to correctly get back the rows being returned from another process. I am > > thinking of some sort of object. > > > > I’m still trying to follow Olivier’s explanation “try to see CALL FORM as > > "execute this project method in the context of this form", similar to > > EXECUTE METHOD IN SUBFORM”. > > > > Anyway, reviewing your previous thoughts. > > > > Appreciate, > > John… > > > > > >> On Mar 9, 2020, at 9:24 AM, Peter Bozek <peter.bo...@gmail.com > >> <mailto:peter.bo...@gmail.com>> wrote: > >> > >> In fact, worker cannot share variables with another process (think of > >> worker as another process running on another processor, not sharing the > >> memory with main process.) But worker can call a method with CALL FORM and > >> pass a parameters to that call, and the parameter can be, for example, an > >> object with embedded values. > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > <http://lists.4d.com/archives.html> > Options: https://lists.4d.com/mailman/options/4d_tech > <https://lists.4d.com/mailman/options/4d_tech> > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > <mailto:4d_tech-unsubscr...@lists.4d.com> > ********************************************************************** > > > -- > -- > > Peter Bozek ********************************************************************** 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 **********************************************************************
