Telerik blogs
  • Web

    JavaScript Timing Events

    This article is taken from W3Schools.   With JavaScript, it is possible to execute some code NOT immediately after a function is called, but after a specified time interval. This is called timing events. It's very easy to time events in JavaScript. The two key methods that are used are: setTimeout() - executes a code some time in the future clearTimeout() - cancels the setTimeout() setTimeout() Syntax var t=setTimeout("javascript statement",milliseconds);  The setTimeout() method returns a value - In the statement above, the value is stored in a variable called t. If you want to cancel this setTimeout(), you can refer to it using the variable name. The first parameter of setTimeout() is a...
    January 30, 2009 2 min read
  • Release

    RadControls for ASP.NET AJAX are now compatible with DotNetNuke 5.0.0

    At the very end of 2008, the DotNetNuke Corporation released a new major version of their web application framework - DNN 5.0.0. Our modules and skinobject PAs were not compatible with the new release because of a change in DotNetNuke's handling of files and subfolders in the PA archive. With the new RadControls for ASP.NET AJAX service pack release (2008.3.1314), we updated our DNN resources to be compatible with the 5.0.0 installer. The new build of the RadControls modules and skinobjects for DotNetNuke can be used in version 5 and 4 as well. If you find an issue with the...
    January 20, 2009 1 min read
  • Web

    How do I pause execution in JavaScript?

    The current article is taken from javascript.faqts Contributors: ha mo, Daniel LaLiberte, Brent Boyer, Martin Honnen, mercury rising,   There is no true wait, sleep, or similar function in either the core JavaScript language or in client side JavaScript. Client side JavaScript however provides     setTimeout('js code here', delayInMilliseconds) which allows you to schedule execution of piece of script and setInterval('js code here', intervalInMilliseconds) which allows you to periodically execute a piece of script. So if you wanted (pseudo code) statement1;  wait (someDelay);  statement2;  you would stuff the code into functions: function statement1 () {      // your code here  }  function statement2 () {      // your code here  }    and call statement1();  setTimeout('statement2()', someDelay);      If you wanted (pseudo...
    December 19, 2008 3 min read
  • Release

    A new series of blog posts coming up

    Hi all,   Telerik’s support is always focused at satisfying customer needs – if you have used our controls for some time now, I guess you have already found that out. If you have just started getting familiar with our products – give us a try ;)   Our support services however, being targeted on our products only, cannot provide you with custom solutions, although we try to help as much as possible. That is why we decided to start a new series of blog posts aimed at different aspects of ASP.NET development. The content is gathered from various newsgroups, blog posts, tutorials in...
    December 19, 2008 2 min read
  • Web ASP.NET AJAX

    Don't Use BODY ONLOAD in ASP.NET AJAX Websites

    In the past developers used <body onload="..."> to execute some script as soon as the page is loaded. Nowadays this is rather old-fashioned, no matter how you look at it. What's more, it doesn't work as expected in ASP.NET AJAX websites. Consider the following example:   <body onload="MyFunction()">    <script type="text/javascript">       function MyFunction()     {        var myAjaxControl = $find("myAjaxControlClientID");        myAjaxControl.doSomething();     }    </script>    </body>    The client-side page load event is fired by the browser as soon as all HTML and scripts have been loaded. However, this happens before the controls' client-side instances have been created. As a result, myAjaxControl will be null and the doSomething() method will trigger a Javascript error. So, a lot better approach...
    December 13, 2008 1 min read