Comments on: Blocking events with blocker lists http://assanka.net/content/tech/2009/12/07/blocking-events-with-blocker-lists/ Just another Arb-assk2009003.turmeric.assanka.com Blogs weblog Fri, 25 Nov 2011 16:18:40 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Andrew Betts http://assanka.net/content/tech/2009/12/07/blocking-events-with-blocker-lists/comment-page-1/#comment-21 Andrew Betts Sun, 02 May 2010 12:42:58 +0000 http://assanka.net/content/tech/?p=56#comment-21 Jakob - In our particular use case we wanted to know what was blocking the scroll, and it was also extremely helpful for debug. But you're right - in a simple use case like the one described in the post, a counter would work fine. Jakob – In our particular use case we wanted to know what was blocking the scroll, and it was also extremely helpful for debug. But you’re right – in a simple use case like the one described in the post, a counter would work fine.

]]> By: Jakob Egger http://assanka.net/content/tech/2009/12/07/blocking-events-with-blocker-lists/comment-page-1/#comment-20 Jakob Egger Mon, 19 Apr 2010 08:55:57 +0000 http://assanka.net/content/tech/?p=56#comment-20 Is there a reason why you use a token list, and not just a counter? Start with the counter at 0. Increase the counter by one every time you start doing something, and decrease the counter by one when you finish something. As long as the counter is zero you can sync scrolling. Incrementing/decrementing a counter is really fast, and checking if a counter is 0 is also very fast. Is there a reason why you use a token list, and not just a counter?

Start with the counter at 0. Increase the counter by one every time you start doing something, and decrease the counter by one when you finish something. As long as the counter is zero you can sync scrolling.

Incrementing/decrementing a counter is really fast, and checking if a counter is 0 is also very fast.

]]>