Detailed Client Side documentation?

2 posts, 1 answers
  1. Eric
    Eric avatar
    82 posts
    Member since:
    Feb 2009

    Posted 20 Mar 2009 Link to this post

    I am still a bit confused by the documentation as it's a bit like launching an R & D project just to get to know the Telerik documentation (IMHO).

    I have not done much javascript in the last few years and I find it quite difficult to differentiate between what is "normal" javascript/dhtml functions from the Telerik specific.
    For instance,
    windows.Close() does not take arguments, as clearly described in http://msdn.microsoft.com/en-us/library/ms536367(VS.85).aspx

    If I look for the arguments that RadWindow.close() take (on the client side), where do I find out?

    The documentation does not say anything http://www.telerik.com/help/aspnet-ajax/window_programmingradwindowmethods.html other than the function exists... and I have just been lucky to find the answer in RadControlsAjaxCourseware.pdf towards p257 with the project \VS Projects\RealEstate\HowToModalDialog

    Is there a less "lucky" way of finding these sort of answers?

    Thanks


    Eric



  2. Answer
    Fiko
    Admin
    Fiko avatar
    1406 posts

    Posted 20 Mar 2009 Link to this post

    Hi Eric,

    The parameter of the RadWindow's close() function is optional. It is used when you need to pass arguments to the OnClientClose event handler of the control ( to return some revalue to the parent page). In this event handler you can get the value of the argument by using the following approach :

    function OnClientClose(oWnd,args) 
       //get the transferred arguments 
       var arg = args.get_argument(); 
       alert(arg); 

    More information about our products and the way they work is available in the followings resources :


    I hope this helps.

    Kind regards,
    Fiko
    the Telerik team


    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top