Right, thought about it again...not a great idea. There's no reason to
expect that you would get exclusive rights to add links to the method
chain...which could lead to some really horrific bugs. Instead, you can get
the same outcome (chained rather than recursion) in any process by posted
work to
Okay, this next post is almost certainly of narrow use and interest but
someone may find it useful.
I've been thinking a lot lately as CALL WORKER as a control structure. It's
not exactly a control structure, but it's easy to see it as more like a
control structure than as a message. 4D hasn't
Cannon Smith writes:
>I'm looking into the idea of setting up a mirrored server. One one hand I want
>to be
>pretty aggressive about sending log files to the mirror-probably every couple
>of minutes.
>On the other hand, I don't want to use "New log file" and then send the log
>file if nothing
As workers and call form are in the air today, I thought that I'd point out
a small detail that some people may like a lot. As we know, 4D doesn't
partition code or scope variables like other languages. Sometimes this
makes us pout. The worker system provides a few helpful wrinkles. Well, you
>
> > Is there some sort of “quick open” functionality for project methods
> that I
> > haven’t found yet?
>
> Yes! Great feature:
>
> METHOD OPEN PATH
> http://doc.4d.com/4Dv16/4D/16/METHOD-OPEN-PATH.301-3037152.en.html
>
P.S. I think that API Pack's version of this feature allows you to open
> On Mar 20, 2017, at 12:45 PM, James Crate via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> It would be nice if the tokenized method name could be used;
We need this in a lot of places. I think it could be as simple as a "Method
name" command that takes the tokenized name and returns the
I’m looking into the idea of setting up a mirrored server. One one hand I want
to be pretty aggressive about sending log files to the mirror—probably every
couple of minutes. On the other hand, I don’t want to use “New log file” and
then send the log file if nothing has changed.
Has anyone
Doug:
You're very welcome.
--
Douglas von Roeder
949-336-2902
On Mon, Mar 20, 2017 at 12:54 PM, Doug Hall via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Will do. Thanks, Douglas!
>
> On Mon, Mar 20, 2017 at 1:52 PM, Douglas von Roeder via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
>
> > Doug:
> >
On Tue, Mar 21, 2017 at 4:45 AM, James Crate via 4D_Tech <
4d_tech@lists.4d.com> wrote:
Hey Jim, it's good to have you chiming in.
> I was looking forward to finally having something better than CALL PROCESS
> available, but it is disappointing to see the level of coupling required
to
> utilize
Will do. Thanks, Douglas!
On Mon, Mar 20, 2017 at 1:52 PM, Douglas von Roeder via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Doug:
>
> Older versions of ALP/4D (ALP8.X) required that you set the horizontal and
> vertical scroll bars to -3.
>
> With newer versions, call
Doug:
Older versions of ALP/4D (ALP8.X) required that you set the horizontal and
vertical scroll bars to -3.
With newer versions, call AL_SetAreaLongProperty($eList;ALP_Area_Visible;0)
to hide or AL_SetAreaLongProperty($eList;ALP_Area_Visible;1) to show the
area.
Check the ALP docs for "ghost"
I go into one form that includes a few ALP areas. I double-click on a
record displayed in one of them, which leads to another form. This form
still has two empty vertical scrollbars from the ALP areas on the previous
form. Anyone know how to fix this?
Thanks,
Doug Hall
On Mar 16, 2017, at 10:28 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com>
wrote:
>
> That's not what 4D's "messages" are, they're commands. In fact, the
> best names for the new commands are probably these:
>
> EXECUTE METHOD IN WINDOW
> EXECUTE METHOD IN WORKER
I was looking forward to
13 matches
Mail list logo
