sure, and the formula we type in the property list evaluates the string “on
data change”, so if you type a method name that does not exist, it is assumed
to be a process variable, and creating or renaming said method does not link
the two. you need to retype the formula expression.
> Le 7 sept. 2018 à 00:28, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> I tested with a recent nightly build (17.226877)
>
> I have [Table_1] but as I type [xx:1] and hit enter, it tokenises as [Table_1]
> same with [:1]
Hi Miyako,
many thanks for testing :-)
I didn't
I tested with a recent nightly build (17.226877)
I have [Table_1] but as I type [xx:1] and hit enter, it tokenises as [Table_1]
same with [:1]
so even though the main place I'd expect tokens to work
is in the context of 4D tags and formula of form objects,
it seems to work in the code editor
o enable the new feature or, if they do, that they give us plenty
> of advance notice. It’s not trivial to make changes like this to a 30 year
> old application with hundreds of tables and a million lines of code.
Hi Richard,
in the table+field token I'm talking about, brackets are *around*, wh
I thought you were saying that these characters were not allowed as of v16 R4
even without enabling the new feature. I’m just hoping that 4D will never
require us to enable the new feature or, if they do, that they give us plenty
of advance notice. It’s not trivial to make changes like this to
> Le 6 sept. 2018 à 08:20, Arnaud de Montard via 4D_Tech <4d_tech@lists.4d.com>
> a écrit :
>
> Hi Tim,
> I did not get your first response from the list. No matter as I can read it
> cited under Richard's response, but I wonder about that gap??
oops I'm wrong. Sorry.
--
Arnaud de
> Le 6 sept. 2018 à 01:31, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> [...]
>
> e.g. [contacts:2] but maybe [contacts] is NOT table #2
Hi Miyako,
to be clearer, this is screen capture of method editor (supposing it's a
similar mechanism to the interpreter):
Hi Tim,
I did not get your first response from the list. No matter as I can read it
cited under Richard's response, but I wonder about that gap??
--
Arnaud de Montard
**
4D Internet Users Group (4D iNUG)
Archive:
it could be that the token syntax for tables and fields has been missed by
engineering when the interpreter was rewritten for object notation.
in fairness, though, I don't think it was ever documented that the table or
field name could be omitted in token syntax.
I know it worked, and sometimes
Hi Richard,
> > * Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in
> > names of tokenized objects.
> I take that to mean they are no loner allowed in “new” names of tokenized
> objects.
I take it to mean they are no longer allowed in tokenized objects, **existing
or
> * Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in
> names of tokenized objects.
I take that to mean they are no loner allowed in “new” names of tokenized
objects.
> Date: Wed, 5 Sep 2018 18:50:28 +
> From: Timothy Penner
>
>> Surely something to do with dot
> Surely something to do with dot notation, but I wonder if it's a bug or
> something I miss?
There is a section of the docs that talks about this:
http://doc.4d.com/4Dv16R4/4D/16-R4/Using-object-notation-preview.300-3303773.en.html#3304590
{
Activating the object notation
Over any versions, 4D
Migrating from v14r5 to v16r6, dot notation on.
In fomulas referencing fields, I have things like this:
TimeStampToText([:2]:3)
In v16r6, such token is no longer recognised ; I've found 2 turnarounds :
1/ add the table/field names before the token:
TimeStampToText ([aTable:2]aField:3)
2/
13 matches
Mail list logo
