Jeremy:
"When Jenner was dithering about vaccination, he was told “Don’t think; try
the experiment”.”
Great quote.
"I may yet run foul of some hidden gremlin which bares its fangs when 4D19
appears, but I tried the experiment and thus far it works like a dream.”
Oh, ye of little faith!
Glad
Tim,
That would seem a very sensible explanation. I’ve just tried setting my worker
method to “can be run in preemptive processes” and, as you would have expected,
it will no longer compile.
So workers intended to do number-crunching and run headless may be marked “can
be pre-emptive” and
erMethod to “Indifferent” it will
complie and you can run it compiled and see the UI from CALL WORKER.
Use “Run” menu from Design to Restart Compiled or Restart Interpreted and use
Test Application to show a menu bar f and the File menu “Show Simple Dialog” to
do just that.
If you have a met
When Jenner was dithering about vaccination, he was told “Don’t think; try the
experiment”.
I may yet run foul of some hidden gremlin which bares its fangs when 4D19
appears, but I tried the experiment and thus far it works like a dream.
Step 1: at startup, call the worker to get things set up
I, collaborative workers may be able to display UI.”
>> Process 1 will display UI in V18, compiled.
>>
>> "But all 4D examples of worker's code use CALL FORM to display UI, so I
>> would not try to display UI from a worker."
>> Call form is a means of communicat
gt; "But all 4D examples of worker's code use CALL FORM to display UI, so I
> would not try to display UI from a worker."
> Call form is a means of communicating with a form. It doesn’t tie back to
> how a process is invoked.
>
In the examples, worker never displays UI, rather us
display UI.”
Process 1 will display UI in V18, compiled.
"But all 4D examples of worker's code use CALL FORM to display UI, so I
would not try to display UI from a worker."
Call form is a means of communicating with a form. It doesn’t tie back to
how a process is invoked.
The fact that
s code use CALL FORM to display UI, so I would
not try to display UI from a worker.
Peter Bozek
**
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Un
> wrote:
>
> > v18.1, Mac
> >
> > What can a worker process do by way of UI? Are there any restrictions?
> >
>
> I am not sure what you want to achieve, but yes, there is a restriction: no
> UI for wor
I’ve used Call worker with the dialog command. Call worker seems to be "yet
another way" to open a process but it doesn’t return a process ID. Similar
to New process, you can name the process and pass parameters. If you’re
closing the dialog and want the process to terminate, just call Kill worker
On Fri, Mar 27, 2020 at 5:29 PM Jeremy Roussak via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> v18.1, Mac
>
> What can a worker process do by way of UI? Are there any restrictions?
>
I am not sure what you want to achieve, but yes, there is a restriction: no
UI for worker. No
I don't see why it would not work. I'm not aware of any real difference between
a worker and a regular 4D process except that a worker has queue of requests
and lives until killed whereas a regular process executes one request and
exists.
I tend to use the 4D progress component with some
v18.1, Mac
What can a worker process do by way of UI? Are there any restrictions?
Situation: I have a task which takes a while to set up but which, once set up,
runs swiftly, perhaps quite often. At present, I just wait for the setup to
complete, but while it’s only a few seconds, it’s boring.
13 matches
Mail list logo
