Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #37493 > unrolled thread

setTimeout( ), with startpoint at t0

Back to article view | Back to comp.lang.javascript

Contents

  setTimeout( ), with startpoint at t0 Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-10-03 04:11 -0700
    Re: setTimeout( ), with startpoint at t0 JJ <jj4public@vfemail.net> - 2019-10-03 19:41 +0700
      Re: setTimeout( ), with startpoint at t0 Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-10-03 08:34 -0700
        Re: setTimeout( ), with startpoint at t0 "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-10-03 21:53 +0200
          Re: setTimeout( ), with startpoint at t0 Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-10-03 14:58 -0700
    Re: setTimeout( ), with startpoint at t0 Arno Welzel <usenet@arnowelzel.de> - 2019-10-04 13:50 +0200
      Re: setTimeout( ), with startpoint at t0 Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-10-04 07:33 -0700
        Re: setTimeout( ), with startpoint at t0 Arno Welzel <usenet@arnowelzel.de> - 2019-10-05 13:58 +0200
          Re: setTimeout( ), with startpoint at t0 Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-10-05 15:44 -0700

#37493 — setTimeout( ), with startpoint at t0

stopRec=setTimeout(STARTREC,interval);

Basicly i want first call immediatly at t0, but this first call will happen after interval?

I tried this.
stopRec=setTimeout(STARTREC,0*interval); 
But i am not sure it works like i think?

Jonas T

[toc] | [next] | [standalone]

#37494

On Thu, 3 Oct 2019 04:11:51 -0700 (PDT), Jonas Thörnvall wrote:
> stopRec=setTimeout(STARTREC,interval);
> 
> Basicly i want first call immediatly at t0, but this first call will happen after interval?
> 
> I tried this.
> stopRec=setTimeout(STARTREC,0*interval); 
> But i am not sure it works like i think?
> 
> Jonas T

setTimeout and setInterval merely create timer events. None of them
immediately execute the timer callbacks.

If you use zero time duration, the callback is basically queued into the
execution flow and will only be executed after the current execution flow
ends, where the JavaScript engine goes into idle state.

[toc] | [prev] | [next] | [standalone]

#37495

Den torsdag 3 oktober 2019 kl. 14:41:44 UTC+2 skrev JJ:
> On Thu, 3 Oct 2019 04:11:51 -0700 (PDT), Jonas Thörnvall wrote:
> > stopRec=setTimeout(STARTREC,interval);
> > 
> > Basicly i want first call immediatly at t0, but this first call will happen after interval?
> > 
> > I tried this.
> > stopRec=setTimeout(STARTREC,0*interval); 
> > But i am not sure it works like i think?
> > 
> > Jonas T
> 
> setTimeout and setInterval merely create timer events. None of them
> immediately execute the timer callbacks.
> 
> If you use zero time duration, the callback is basically queued into the
> execution flow and will only be executed after the current execution flow
> ends, where the JavaScript engine goes into idle state.

It is a bit weird though if you write, 8*interval "just the first call will take  8 times interval"?

[toc] | [prev] | [next] | [standalone]

#37496

<jonas.thornvall@gmail.com> wrote on 03 Oct 2019 in comp.lang.javascript: 

> It is a bit weird though if you write, 8*interval "just the first call
> will take  8 times interval"? 

If you think so, don't do it!

=======

Seems to me you are mixing setTimeout() and setInterval() ideas.

setTimeout() strictly has no "interval-time", as it fires only once at most.

If you construct an repeated happening starting at time zero, 
the called function should set the setTimeout() again.

========= Using setTimeout():

=========
let timeoutPointer;
const timeoutFunction = () => {
    	doWhatYouWantItToDo();
    	timeoutPointer = setTimeout(timeoutFunction,100);
};
timeoutFunction();
==========

A problem could arize here, as doWhatYouWantItToDo() time spend is added to 
the repeat time each time. Timing of multiple repeates is inexact in total, 
the time between individual repeates is rather exact.

========= Using setInterval():

=========
let intervalPointer;
const intervalFunction = () => {
    	doWhatYouWantItToDo();
};
intervalPointer = setInterval(intervalFunction,100);
intervalFunction(); /* FIRST TIME ONLY */
==========

A problem could arize here, as doWhatYouWantItToDo() time spend overruns the 
repeat time, and you could even have 2 versions in the queue running 
directly after eachother. Timing of multiple repeates is rather exact, 
individual firings in the queue could be far of.



-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#37497

Den torsdag 3 oktober 2019 kl. 21:53:47 UTC+2 skrev Evertjan.:
> <jonas.thornvall@gmail.com> wrote on 03 Oct 2019 in comp.lang.javascript: 
> 
> > It is a bit weird though if you write, 8*interval "just the first call
> > will take  8 times interval"? 
> 
> If you think so, don't do it!
> 
> =======
> 
> Seems to me you are mixing setTimeout() and setInterval() ideas.
> 
> setTimeout() strictly has no "interval-time", as it fires only once at most.
> 
> If you construct an repeated happening starting at time zero, 
> the called function should set the setTimeout() again.
> 
> ========= Using setTimeout():
> 
> =========
> let timeoutPointer;
> const timeoutFunction = () => {
>     	doWhatYouWantItToDo();
>     	timeoutPointer = setTimeout(timeoutFunction,100);
> };
> timeoutFunction();
> ==========
> 
> A problem could arize here, as doWhatYouWantItToDo() time spend is added to 
> the repeat time each time. Timing of multiple repeates is inexact in total, 
> the time between individual repeates is rather exact.
> 
> ========= Using setInterval():
> 
> =========
> let intervalPointer;
> const intervalFunction = () => {
>     	doWhatYouWantItToDo();
> };
> intervalPointer = setInterval(intervalFunction,100);
> intervalFunction(); /* FIRST TIME ONLY */
> ==========
> 
> A problem could arize here, as doWhatYouWantItToDo() time spend overruns the 
> repeat time, and you could even have 2 versions in the queue running 
> directly after eachother. Timing of multiple repeates is rather exact, 
> individual firings in the queue could be far of.
> 
> 
> 
> -- 
> Evertjan.
> The Netherlands.
> (Please change the x'es to dots in my emailaddress)

Yeah you are correct Evertjan i mixed it up, "a timeout called a interval", and i got confused about what was going on.

[toc] | [prev] | [next] | [standalone]

#37498

On 03.10.19 13:11, Jonas Thörnvall wrote:

> stopRec=setTimeout(STARTREC,interval);
> 
> Basicly i want first call immediatly at t0, but this first call will happen after interval?

What is "t0"? What is "STARTREC"?

> I tried this.
> stopRec=setTimeout(STARTREC,0*interval); 
> But i am not sure it works like i think?

See
<https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout>


-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#37499

Den fredag 4 oktober 2019 kl. 13:50:36 UTC+2 skrev Arno Welzel:
> On 03.10.19 13:11, Jonas Thörnvall wrote:
> 
> > stopRec=setTimeout(STARTREC,interval);
> > 
> > Basicly i want first call immediatly at t0, but this first call will happen after interval?
> 
> What is "t0"? What is "STARTREC"?
> 
> > I tried this.
> > stopRec=setTimeout(STARTREC,0*interval); 
> > But i am not sure it works like i think?
> 
> See
> <https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout>
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

Well t0 is Time zero 0 ms, what startRec is, is not interesting. If you want to find out look here.

https://midisequenser.000webhostapp.com/

I made a corrector for recording latency today. If you have a music keyboard try it, but maybe there is no. On my computers there is none or rather negative for some reason seems impossible. But if you have you can correct "the music you play up, vs the midi you play in".

[toc] | [prev] | [next] | [standalone]

#37501

Jonas Thörnvall:

> Den fredag 4 oktober 2019 kl. 13:50:36 UTC+2 skrev Arno Welzel:
>> On 03.10.19 13:11, Jonas Thörnvall wrote:
>>
>>> stopRec=setTimeout(STARTREC,interval);
>>>
>>> Basicly i want first call immediatly at t0, but this first call will happen after interval?
>>
>> What is "t0"? What is "STARTREC"?
>>
>>> I tried this.
>>> stopRec=setTimeout(STARTREC,0*interval); 
>>> But i am not sure it works like i think?
>>
>> See
>> <https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout>
>>
>>
>> -- 
>> Arno Welzel
>> https://arnowelzel.de
> 
> Well t0 is Time zero 0 ms, what startRec is, is not interesting. If you want to find out look here.

Why do you even use setTimeout() then and not just call STARTREC directly?


-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#37504

Den lördag 5 oktober 2019 kl. 13:58:25 UTC+2 skrev Arno Welzel:
> Jonas Thörnvall:
> 
> > Den fredag 4 oktober 2019 kl. 13:50:36 UTC+2 skrev Arno Welzel:
> >> On 03.10.19 13:11, Jonas Thörnvall wrote:
> >>
> >>> stopRec=setTimeout(STARTREC,interval);
> >>>
> >>> Basicly i want first call immediatly at t0, but this first call will happen after interval?
> >>
> >> What is "t0"? What is "STARTREC"?
> >>
> >>> I tried this.
> >>> stopRec=setTimeout(STARTREC,0*interval); 
> >>> But i am not sure it works like i think?
> >>
> >> See
> >> <https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout>
> >>
> >>
> >> -- 
> >> Arno Welzel
> >> https://arnowelzel.de
> > 
> > Well t0 is Time zero 0 ms, what startRec is, is not interesting. If you want to find out look here.
> 
> Why do you even use setTimeout() then and not just call STARTREC directly?
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de
Well i think it is leftover from when recording and play was separate, and i still use the clearTimeout to stop a scrollbar animation and the playup of metronome. 

if (tottime>re){ clearTimeout(stopRec);STOPREC();} 

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web