You need to declare timer outside the function. Otherwise, you get a brand new variable on each function invocation. var timer; function endAndStartTimer() { window.clearTimeout(timer); //var millisecBeforeRedirect = 10000; timer = window.setTimeout(function(){alert(‘Hello!’);},10000); }
I see 4 issues with your code: In your timer method you are always setting your current count to 10 You try to update the state in render method You do not use setState method to actually change the state You are not storing your intervalId in the state Let’s try to fix that: componentDidMount: … Read more
Implement using useEffect hook: function Search() { const [searchTerm, setSearchTerm] = useState(”) useEffect(() => { const delayDebounceFn = setTimeout(() => { console.log(searchTerm) // Send Axios request here }, 3000) return () => clearTimeout(delayDebounceFn) }, [searchTerm]) return ( <input autoFocus type=”text” autoComplete=”off” className=”live-search-field” placeholder=”Search here…” onChange={(e) => setSearchTerm(e.target.value)} /> ) }
Update (2017) Here in 2017, Promises are built into JavaScript, they were added by the ES2015 spec (polyfills are available for outdated environments like IE8-IE11). The syntax they went with uses a callback you pass into the Promise constructor (the Promise executor) which receives the functions for resolving/rejecting the promise as arguments. First, since async … Read more
As always with Android there’s lots of ways to do this, but assuming you simply want to run a piece of code a little bit later on the same thread, I use this: new android.os.Handler(Looper.getMainLooper()).postDelayed( new Runnable() { public void run() { Log.i(“tag”, “This’ll run 300 milliseconds later”); } }, 300); .. this is pretty … Read more
To keep the promise chain going, you can’t use setTimeout() the way you did because you aren’t returning a promise from the .then() handler – you’re returning it from the setTimeout() callback which does you no good. Instead, you can make a simple little delay function like this: function delay(t, v) { return new Promise(resolve … Read more
The setInterval method returns a handle that you can use to clear the interval. If you want the function to return it, you just return the result of the method call: function intervalTrigger() { return window.setInterval( function() { if (timedCount >= markers.length) { timedCount = 0; } google.maps.event.trigger(markers[timedCount], “click”); timedCount++; }, 5000 ); }; var … Read more
I recently asked about this and it is behaviour by design. When a tab is inactive, only at a maximum of once per second the function is called. Here is the code change. Perhaps this will help: How can I make setInterval also work when a tab is inactive in Chrome? TL;DR: use Web Workers.
Defined return () => { /*code/* } function inside useEffect runs every time useEffect runs (except first render on component mount) and on component unmount (if you don’t display component any more). This is a working way to use and clear timeouts or intervals: Sandbox example. import { useState, useEffect } from “react”; const delay … Read more
Just to add to what everyone else have said about setTimeout: If you want to call a function with a parameter in the future, you need to set up some anonymous function calls. You need to pass the function as an argument for it to be called later. In effect this means without brackets behind … Read more