Hello :)
In our application we have tab-view design. The application overall is very complex and resource-consuming. Every tab has it's own html content, which is placed in html place holder.
The problem: when a person switches between tabs the html content is not persisted and for instance if a person had some form with ricj text editor and he or she entered a lot text, this text would be gone.
I know there is KeepContentInMemory property which does what I need, but it's good only for simple and light-weight applications, in my case it breaks the interface leaving the partial content of different pages on the screen.
During further investigation we have set up a virtual machine with old Silverlight 3 version and telerik controls for Silverlight 3 and above described problem appears to be gone.
Unfortunately we're not able to use Silverlight 3 controls as we migrated our development and productions environment to Silverlight 5.
Could advise us about the differences in implementation of RadHtmlPlaceHolder for Silverlight 3 and Silverlight 5?
Is there completely other way rendering the html content inside Silveright 5 control with help of Telerik controls?
Any help is greatly appreciated :)
In our application we have tab-view design. The application overall is very complex and resource-consuming. Every tab has it's own html content, which is placed in html place holder.
The problem: when a person switches between tabs the html content is not persisted and for instance if a person had some form with ricj text editor and he or she entered a lot text, this text would be gone.
I know there is KeepContentInMemory property which does what I need, but it's good only for simple and light-weight applications, in my case it breaks the interface leaving the partial content of different pages on the screen.
During further investigation we have set up a virtual machine with old Silverlight 3 version and telerik controls for Silverlight 3 and above described problem appears to be gone.
Unfortunately we're not able to use Silverlight 3 controls as we migrated our development and productions environment to Silverlight 5.
Could advise us about the differences in implementation of RadHtmlPlaceHolder for Silverlight 3 and Silverlight 5?
Is there completely other way rendering the html content inside Silveright 5 control with help of Telerik controls?
Any help is greatly appreciated :)
1 Answer, 1 is accepted
0
Hi Oleg,
This is a complex issue due to the integration of these two controls TabControl and HtmlPlaceHolder. Furthermore the KeppingContent in memory and preserving the SL Content are independend features too complex on their own. This is just to say that it is hard to say whether exactly the issue is in the HTMLPlaceholder or in the RadTabControl or whether it is a limitation in the SL Framework. We can only say that we are aware of this issue and it is logged previously in our PITS.
During the years, RadTabControl is the control from these two that has evolved a lot. But this is just a shoot in the dark. We need a much deeper investigation to perform to answer precisely.
Regards,
Petar Mladenov
Telerik
This is a complex issue due to the integration of these two controls TabControl and HtmlPlaceHolder. Furthermore the KeppingContent in memory and preserving the SL Content are independend features too complex on their own. This is just to say that it is hard to say whether exactly the issue is in the HTMLPlaceholder or in the RadTabControl or whether it is a limitation in the SL Framework. We can only say that we are aware of this issue and it is logged previously in our PITS.
During the years, RadTabControl is the control from these two that has evolved a lot. But this is just a shoot in the dark. We need a much deeper investigation to perform to answer precisely.
Regards,
Petar Mladenov
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for SILVERLIGHT.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>