A lot more scalable too - one server process per client dedicated to the UI, no
matter how many windows are open locally...
> On Apr 29, 2020, at 11:52 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Where workers come in is to do, well - work. All the heavy processing be it
>
Pat,
To expand a little on the other comments for you to be able to _keep_
windows open when you use the * they must be opened from an existing
window. Otherwise they pop open and then close again. Another difference is
when you call
DIALOG("myForm";*)
the method doesn't stop with DIALOG. It
Pat:
The asterisk was added to the Dialog command in V12. That was all well and
good but the developer had to get creative to communicate with a given
window within a process because Call process was picked up by the frontmost
window in a process.
The “Call form” command (late V15) allows us to
workers
Chuck Miller Voice: (617) 739-0306
Informed Solutions, Inc. Fax: (617) 232-1064
mailto:cjmillerinformed-solutions.com
Brookline, MA 02446 USA Registered 4D Developer
DIALOG with the More Power parameter (*)... it's not a dream!
> On Apr 29, 2020, at 7:17 PM, Pat Bensky via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Maybe it was in a dream ... but I'm sure I recall reading something about a
> new feature (v17) that allows more than one window to be open
Maybe it was in a dream ... but I'm sure I recall reading something about a
new feature (v17) that allows more than one window to be open within a
process. But now I can't find that info. Did I imagine it?
Pat
--
*
CatBase - Top Dog in Data
6 matches
Mail list logo
