Navigate to RadPane

2 posts, 0 answers
  1. Brad
    Brad avatar
    8 posts
    Member since:
    Jun 2009

    Posted 04 Jun 2009 Link to this post

    I have a page with a splitter (Horizontal) Top & Bottom. The bottom page contains a RadPane with an ID="Main" and the ContentUrl defaulted to a specific page. from the Top Pane I have the Rad Toolbar with a Button that I have set the NavigateUrl to another page and the Target="Main", but when you click the button it redirects the entire window to that page not the RadPane (ID="Main"). I know I could catch this in the Post back event and set the ContentUrl via Code but I would rather not have the PostBack.
  2. Paul
    Admin
    Paul avatar
    4281 posts

    Posted 08 Jun 2009 Link to this post

    Hello Brad,

    We tested the code snippet below using the latest version of the control, and everything runs just fine.

    <form id="form1" runat="server">  
        <telerik:RadScriptManager ID="RadScriptManager1" runat="server">  
        </telerik:RadScriptManager> 
        <telerik:RadSplitter ID="RadSplitter1" runat="server" Orientation="Horizontal" Height="100%" 
            Width="100%">  
            <telerik:RadPane ID="RadPane1" runat="server" Height="36px" Width="100%">  
                <telerik:RadToolBar ID="RadToolBar1" runat="server">  
                    <Items> 
                        <telerik:RadToolBarButton runat="server" NavigateUrl="http://www.telerik.com" Target="RadPane2" 
                            Text="Button 0">  
                        </telerik:RadToolBarButton> 
                    </Items> 
                </telerik:RadToolBar> 
            </telerik:RadPane> 
            <telerik:RadPane ID="RadPane2" runat="server" ContentUrl="blank.html" Height="500px">  
            </telerik:RadPane> 
        </telerik:RadSplitter> 
        </form> 

    Let us know what's different in your case.

    Sincerely yours,
    Paul
    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