Panelbar Causes Undesired Effect

3 posts, 1 answers
  1. PJ Rodriguez
    PJ  Rodriguez avatar
    37 posts
    Member since:
    Feb 2005

    Posted 23 Nov 2010 Link to this post

    I have a radpanelbar  that I use to call a radwindow during an itemclick event. This works as advertised, the problem is that the itemclick event seems to happen again if I cause another postback.

    For example, if the user clicks the radpanelbar and fires the itemclick event which opens window1--I then close window1. Now I click on a radtreeview control which causes another postback and for some reason, the radpanelbar itemclick event fires again which opens window1 again even though button1 does not call for window1 to open.

        Private Sub RadTreeView1_NodeClick(ByVal sender As Object, ByVal e As Telerik.Web.UI.RadTreeNodeEventArgs) Handles RadTreeView1.NodeClick
            Dim clickedNode As RadTreeNode = e.Node
            'RadPanelBar1.DataBind()

            If clickedNode.ParentNode.Text = "Other Approvals" Then
                abview1.Visible = True
                abview1.idAgendaBills = clickedNode.Value
                abview1.DataBind()
            Else
                hideControls()
    end sub
            End If

    Obviously I don't want that to happen. Are there any workarounds to this? Thanks!
  2. Answer
    Peter
    Admin
    Peter avatar
    6637 posts

    Posted 26 Nov 2010 Link to this post

    Hi PJ Rodriguez,

    This is unusual. Can you send us the entire code of your implementation? Or, even better, open a support ticket and send us a simple working demo of the issue.


    Kind regards,
    Peter
    the Telerik team
    Browse the vast support resources we have to jumpstart your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. PJ Rodriguez
    PJ  Rodriguez avatar
    37 posts
    Member since:
    Feb 2005

    Posted 29 Nov 2010 Link to this post

    Well, this is embarassing but the fix was clearing the Visual Studio cache, performing a clean in VS, and doing a rebuild and that fixed the issue. I should have done that first before postnig here but I was so frustrated after working on a fix for so long. In any case, thank you for the reply.


    PJ
Back to Top