Hello,
I use almost for every RadSplitter in my project the VisibleDuringInit=false setting.
After updating with the 14 januari update, this setting doesn't work anymore.
In other words the behauvior is like the setting is VisibleDuringInit=true.
I have read in the version notes, that the splitter is updated to the way the splitter hides its content.
But in my case there is no hiding anymore.
After testing it seems that it doesn't work with splitters with Orientation="Horizontal.
With Orientation="Vertical" it works ok in most cases. (but i use mostly the horizontal orientation)
This is only happening in IE7. In FF everything works good.
I like to hear some advice, how to solve this.
I use almost for every RadSplitter in my project the VisibleDuringInit=false setting.
After updating with the 14 januari update, this setting doesn't work anymore.
In other words the behauvior is like the setting is VisibleDuringInit=true.
I have read in the version notes, that the splitter is updated to the way the splitter hides its content.
But in my case there is no hiding anymore.
After testing it seems that it doesn't work with splitters with Orientation="Horizontal.
With Orientation="Vertical" it works ok in most cases. (but i use mostly the horizontal orientation)
This is only happening in IE7. In FF everything works good.
I like to hear some advice, how to solve this.
2 Answers, 1 is accepted
0
Accepted
Hi Marco,
I already answered your support ticket with the same question. I will give the information here as well, so that it is available to all, who might run into the same problem:
***
The problem is caused from the FullScreenMode property that you have applied to your main RadSplitter:
As soon as you remove this property, you will get the expected result. You have configured your page correctly for the RadSplitter to occupy 100% of the height of its parent and removing this property would not change the layout of the page. You should just add Width=100% to get the effect of the FullScreenMode.
Yes, we did change the implementation of the VisibleDuringInit property for performance reasons. Now, when you have a lot of HTML in the RadPanes and VisibleDuringInit=false, the RadSplitter loads notably faster. However, the new implementation does not work as expected when you set FullScreenMode=true.
The FullScreenMode property was introduced so that you can configure the splitter to become as high and as wide as the browser window when the splitter is a direct child of the FORM element and without the necessity to set the splitter's Width and Height properties and the Height of the HTML, BODY and FORM elements. However, it works only in few cases as people expect it to. That is why we decided to change the implementation of the VisibleDuringInit property and mark the FullScreenMode property as obsolete (we will do this for the next update of the suite).
***
Regards,
Tsvetie
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
I already answered your support ticket with the same question. I will give the information here as well, so that it is available to all, who might run into the same problem:
***
The problem is caused from the FullScreenMode property that you have applied to your main RadSplitter:
| <telerik:RadSplitter ID="MainSplitter" runat="server" |
| FullScreenMode="true" Orientation="Vertical" |
| VisibleDuringInit="false" Height="100%"> |
As soon as you remove this property, you will get the expected result. You have configured your page correctly for the RadSplitter to occupy 100% of the height of its parent and removing this property would not change the layout of the page. You should just add Width=100% to get the effect of the FullScreenMode.
Yes, we did change the implementation of the VisibleDuringInit property for performance reasons. Now, when you have a lot of HTML in the RadPanes and VisibleDuringInit=false, the RadSplitter loads notably faster. However, the new implementation does not work as expected when you set FullScreenMode=true.
The FullScreenMode property was introduced so that you can configure the splitter to become as high and as wide as the browser window when the splitter is a direct child of the FORM element and without the necessity to set the splitter's Width and Height properties and the Height of the HTML, BODY and FORM elements. However, it works only in few cases as people expect it to. That is why we decided to change the implementation of the VisibleDuringInit property and mark the FullScreenMode property as obsolete (we will do this for the next update of the suite).
***
Regards,
Tsvetie
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Marco
Top achievements
Rank 1
Rank 1
answered on 11 Feb 2009, 12:46 AM
Hello Tsvetie ,
Your solution works perfect and the problem is solved.
Thank you
Marco
Your solution works perfect and the problem is solved.
Thank you
Marco