Javascript code runs only on one thread. setTimeout schedules a function to run later. So in js when all currently running code finish its execution , event loop will look for any other event. So setTimeout( .. 0) will make code run after the current loop. console.log(“I’m message from outside timeout”); will be first scheduled … Read more
while (Date.now() – nu < 1000) {} doesn’t simulate a long running task that is syncronous. It is a long running task that is syncronous. Promises are a way to manage asynchronous code, not a way to make code asynchronous, nor a way to simulate multithreading. For that, you need to look at workers. Web … Read more
It won’t necessarily run right away, neither will explicitly setting the delay to 0. The reason is that setTimeout removes the function from the execution queue and it will only be invoked after JavaScript has finished with the current execution queue. console.log(1); setTimeout(function() {console.log(2)}); console.log(3); console.log(4); console.log(5); //console logs 1,3,4,5,2 for more details see http://javascriptweblog.wordpress.com/2010/06/28/understanding-javascript-timers/
In basic words $timeout refers to angularjs when setTimeout – to JavaScript. If you still think to use setTimeout therefore you need invoke $scope.$apply() after As a side note I suggest you to read How do I “think in AngularJS” if I have a jQuery background? post and AngularJS: use $timeout, not setTimeout Example 1: … Read more
You need to use Promises for this. They are available in ES6 but can be polyfilled quite easily: function x() { return new Promise((resolve, reject) => { setTimeout(() => { resolve(‘done!’); }); }); } x().then((done) => { console.log(done); // –> ‘done!’ }); With async/await in ES2017 it becomes nicer if inside an async function: async … Read more
I think that most people are getting at the reason why this isn’t working, but I thought I would provide you with updated code. It is pretty much the same as yours, except that it assigns the timeout to a variable so that it can be cleared. Also, the anonymous function in a setTimeout is … Read more
The overall approach varies based on your Jasmine version. Jasmine 1.3 You can use waitsFor: it( “Disable all submit buttons”, function() { // Get a button var $button = $( ‘#ai1ec_subscribe_users’ ); // Call the function utility_functions.block_all_submit_and_ajax( $button.get(0) ); // Wait 100ms for all elements to be disabled. waitsFor(‘button to be disabled’, function(){ var found … Read more
Is the code contained in a function? function test() { setTimeout(…); // code that you cannot modify? } In that case, you could prevent the function from further execution, and then run it again: function test(flag) { if(!flag) { setTimeout(function() { alert(); test(true); }, 5000); return; } // code that you cannot modify }
This will make the second function wait 2 seconds (2000 milliseconds) before executing: $(‘.icon’).hover(function() { clearTimeout($(this).data(‘timeout’)); $(‘li.icon > ul’).slideDown(‘fast’); }, function() { var t = setTimeout(function() { $(‘li.icon > ul’).slideUp(‘fast’); }, 2000); $(this).data(‘timeout’, t); }); It also clears the timeout when the user hovers back in to avoid crazy behavior. This is not a very … 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