the same question was posted on the forums a couple of days ago.
time values are represented in milliseconds,
so a date string, the first part of which is the year 2017,
approximates to 2 seconds past midnight.
> 2017/05/25 8:32、Tom Dillon via 4D_Tech <4d_tech@lists.4d.com> のメール：
>
> OB
I suppose I'm missing something obvious...
Within an object "created":"2014-02-01T09:28:56"
OB Get is returning the correct date with:
OB Get($OBGenInfo;"created";Is date) with
But, time always returns ?00:00:02? using:
OB Get($OBGenInfo;"created";Is time)
Or is the time a count down 'till
> Le 24 mai 2017 à 22:14, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> seems like a bug to me
> :)
v17 feature.
non-disclosure agreement.
--
Arnaud de Montard
**
4D Internet Users Group (4D iNUG)
seems like a bug to me
:)
On Wed, 24 May 2017 14:16:32 -0500, Keith Culotta via 4D_Tech wrote:
> In v16 interpreted
>
> C_TEXT($t)
> C_POINTER($p1;$p2)
>
> $t:="A"
> $p1:=(->$t)
> $p2:=(->$p1)
>
> ALERT($p2->->) // Error
> ALERT(($p2->)->) // A
> ALERT(String(Type($p2->->))) // 2
>
Thanks to all who responded.
Tim Penner and Charles Miller -
It was the compatibility setting "Use 4DVAR Comments instead of Brackets"
This explains why a new database worked correctly. You can not even access
the option there. Since the structure has been through multiple versions of
4D
In v16 interpreted
C_TEXT($t)
C_POINTER($p1;$p2)
$t:="A"
$p1:=(->$t)
$p2:=(->$p1)
ALERT($p2->->) // Error
ALERT(($p2->)->) // A
ALERT(String(Type($p2->->))) // 2
ALERT(String(Type(($p2->)->))) // 2
Type and Alert have different tolerances?
Keith - CDI
> On May 24, 2017, at 1:50 PM, Chip
6 matches
Mail list logo
