Kirk, As neither an attender nor a partner, I can’t see that presentation (yet; I assume it will become more generally available one day). I need to look more closely at DIALOG(*), but it does seem to me that CALL FORM can be pretty useful as a means of interprocess communication as well as inter-window.
However, the window ordering problem was caused, as so often, by my own idiocy and now that I can’t blame 4D for it, I’ve been forced to fix my self-introduced bug on my own. Jeremy > On 11 Sep 2019, at 20:58, Kirk Brooks via 4D_Tech <[email protected]> > wrote: > > Jeremy, > On Wed, Sep 11, 2019 at 1:13 PM Jeremy Roussak via 4D_Tech < > [email protected]> wrote: > >> ... CALL FORM as a method of interprocess communication. ... > > > You might want to take a look at John Baughman's preso from the last > Summit: > https://kb.4d.com/assetid=78028 > > Long story short, CALL FORM is intended for comms between forms (or windows > really). It's particularly great with windows in the same process. Multiple > open forms in a single process is a new capability of DIALOG(*). This > scheme works well with the ORDA tools. If you are doing classic 4D it's > probably going to be a lot more fussy. > > -- > Kirk Brooks > San Francisco, CA > ======================= > > What can be said, can be said clearly, > and what you can’t say, you should shut up about > > *Wittgenstein and the Computer * > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
