Andrew Lawrence
Top achievements
Rank 1
Rank 1
Andrew Lawrence
asked on 27 Jul 2011, 06:02 AM
In release 2011.1 519 an issue was fixed according to Telerik's release notes: Fixed: RadMultiPage: RenderSelectedPageOnly property was applied
multiple times and too early in the Page Lifecycle, setting non-selected
PageViews to Visible=false and causing troubles persisting state of
some of the controls inside the views
This change seems to be causing me problems now.
It seems that the PageView only becomes visible now very late in the cycle! During Page.LoadComplete the selected page view seems to still be invisible, only becoming visible by PreRender.
This is making it difficult to deal with child controls of the PageView as the controls appear to be invisible until Page.PreRender, by which stage it is often too late to handle certain tasks.
Can you confirm this is correct?
The old behaviour wasn't causing me problems (as far as I am aware). Perhaps I could work around these new changes by manually setting the PageView to visible in my own code. Do you know of any workaround?
This change seems to be causing me problems now.
It seems that the PageView only becomes visible now very late in the cycle! During Page.LoadComplete the selected page view seems to still be invisible, only becoming visible by PreRender.
This is making it difficult to deal with child controls of the PageView as the controls appear to be invisible until Page.PreRender, by which stage it is often too late to handle certain tasks.
Can you confirm this is correct?
The old behaviour wasn't causing me problems (as far as I am aware). Perhaps I could work around these new changes by manually setting the PageView to visible in my own code. Do you know of any workaround?
1 Answer, 1 is accepted
0
Hi Andrew,
You are right that with the current implementation of the controls the Visible property of the selected pageview is applied late in the page life cycle. This happens in the PreRenderComplete event.
If you need to know which pageview will be visible after the post-back you could use the Selected property and manipulate the content controls in earlier stage of the page life cycle like Page_Load for instance.
All the best,
Dimitar Terziev
the Telerik team
You are right that with the current implementation of the controls the Visible property of the selected pageview is applied late in the page life cycle. This happens in the PreRenderComplete event.
If you need to know which pageview will be visible after the post-back you could use the Selected property and manipulate the content controls in earlier stage of the page life cycle like Page_Load for instance.
All the best,
Dimitar Terziev
the Telerik team
Browse the vast support resources we have to jump start 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.