the the question is :
How are these numbers generated?
maybe there is a typing issue (integer) or a division issue (div by zero)?
as we all know - longint should hold aprox 2.1 billion
> Hi
> More information
> The contents of the Array <>StartSampleArray are
>
> Interpreted
> 88200
> 7959168
>
Hi
More information
The contents of the Array <>StartSampleArray are
Interpreted
88200
7959168
14775852
20392428
26655216
33432504
40425000
48037248
55659492
62072808
Compliled
88200
7959168
14775852
20392428
26655216
-23833727
-16841231
-9228983
-1606739
4806577
I seem to be getting an overflo
Samples, not Seconds
devide seconds by 44100
-pm
On Tue, Feb 14, 2017 at 9:45 PM, Chip Scheide <4d_o...@pghrepository.org>
wrote:
> not sure what you are doing..
> 26655216 is more then 7400 hours
>
> If $Duration is negative then <>StartSampleArray{$i} is larger then the
> next array element va
On Tue, Feb 14, 2017 at 4:30 PM, Peter Mew via 4D_Tech <4d_tech@lists.4d.com
> wrote:
> Hi
> This snippet of code is in a loop, of typically 10 to 20 items.
> The Array <>StartsampleArray holds the start time, in samples, of the
> tracks on a CD.
> It all works fine interpreted, but when compiled,
not sure what you are doing..
26655216 is more then 7400 hours
If $Duration is negative then <>StartSampleArray{$i} is larger then the
next array element value (<>StartSampleArray{$i+1})
Since 26655216 seconds is 7400 hours, or if the the value 26+ million
is milliseconds is still over 7.4 hour
Nice post Tim, a good resource.
You know I just recently noticed how much the lowly String command has
changed. And not just to accommodate the ISO Date format but to basically
support any input except blobs, pictures and c-objects. Illustrates your
point of looking at the docs for things I think
Hi
This snippet of code is in a loop, of typically 10 to 20 items.
The Array <>StartsampleArray holds the start time, in samples, of the
tracks on a CD.
It all works fine interpreted, but when compiled, when
<>StartSampleArray{$i} exceeds around 26655216 or thereabouts $Duration
turns negative, and
On Feb 14, 2017, at 2:00 PM, Thomas Maul wrote:
> There is a limit, see documentation:
> http://doc.4d.com/4Dv15/4D/15.4/Field-and-variable-objects.300-3285416.en.html
>
> "Note: Text variables and fields in forms are designed to display contents of
> a "reasonable" size. Beyond several tens of
This goes in line with something I learned after submitting a bug for BASE64
ENCODE. The formula was changed so there was one very, very long line of
code for large amounts of data. This drawing for this line suddenly stopped
after something like 37K characters. It turns out Windows has a visual li
Looks like the limiting factor is the number of lines in the scrollable text
area. I did verify that all the data is in the variable. If I resize the text
area to be smaller so there's a lot of word wrapping (and extra lines), the
data gets truncated. If I widen the area so each SQL statement i
> > There seems to be about a 383K character limit in text variables on
> > a form. I
Yes - no.
There is a limit, see documentation:
http://doc.4d.com/4Dv15/4D/15.4/Field-and-variable-objects.300-3285416.en.html
"Note: Text variables and fields in forms are designed to display contents of a
"r
Jeff,
I just tried it and it worked properly (mostly). I put a million characters on
the clipboard, pasted it to a text variable on a form and checked the length.
Oddly enough the length showed 999,999.
I tried putting a few control characters in there just for kicks, but it still
worked.
You
> Le 14 févr. 2017 à 03:11, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> Thanks Tim - does it matter if it's a field or a variable on the form?
Hi Jeffrey,
I noticed I couldn't scroll down above "a certain limit" yesterday after having
pasted some json text.
The container
Peter,
so.. No!
v13 does NOT have this command.
On Tue, 14 Feb 2017 04:51:33 -0700 (MST), Peter Lerch via 4D_Tech wrote:
> Chip Scheide wrote
>> so...
>> No
>
> so...
> Yes
>
> ARRAY LONGINT($MyFormEvents;1)
> $MyFormEvents{1}:=On Unload
> OBJECT SET EVENTS(*;"";$MyFormEvents;Enable events othe
Chip Scheide wrote
> so...
> No
so...
Yes
ARRAY LONGINT($MyFormEvents;1)
$MyFormEvents{1}:=On Unload
OBJECT SET EVENTS(*;"";$MyFormEvents;Enable events others unchanged)
--
View this message in context:
http://4d.1045681.n5.nabble.com/v13-Any-way-to-set-a-Form-Property-programatically-tp5750
Good morning
I was wondering if the behaviour of TRACE on v16 Server has changed?
I have taken a v15 db (interpretted) and converted it to v16. I
specifically put a syntax error into the On Server Startup method.
In v15 the Syntx Error window appears and I can then click TRACE.
However in v16 t
16 matches
Mail list logo