Hi,
I am using the 2008 Q2 release.
My objective is to use the external Skins included in the SDK so I can make modifications.
On my test ASPX page when I use the embedded skins everything seems ok.
RadEditor1.EnableEmbeddedSkins = True
RadEditor1.Skin = "Default"
However by merely including the CSS files from the SDK (listed below) the form and the editor display with various weird side effects *vertical scrollbar does not appear in the content area when needed
*update panel color is gray and there's a dashed border
etc etc.
(note:this happens without setting EnableEmbeddedSkins =false).
ARE THE ETERNAL SKINS INCLUDED IN THE SDK up to date/valid etc?
Also, your solution for making the editor appear as a text box (http://www.telerik.com/DEMOS/ASPNET/Prometheus/Editor/Examples/EditorAsTextBox/DefaultCS.aspx) works fine with the DEFAULT skin but NOT with the Office2007 skin (using embedded skins)!!!!!
I am using the 2008 Q2 release.
My objective is to use the external Skins included in the SDK so I can make modifications.
On my test ASPX page when I use the embedded skins everything seems ok.
RadEditor1.EnableEmbeddedSkins = True
RadEditor1.Skin = "Default"
However by merely including the CSS files from the SDK (listed below) the form and the editor display with various weird side effects *vertical scrollbar does not appear in the content area when needed
*update panel color is gray and there's a dashed border
etc etc.
(note:this happens without setting EnableEmbeddedSkins =false).
ARE THE ETERNAL SKINS INCLUDED IN THE SDK up to date/valid etc?
Also, your solution for making the editor appear as a text box (http://www.telerik.com/DEMOS/ASPNET/Prometheus/Editor/Examples/EditorAsTextBox/DefaultCS.aspx) works fine with the DEFAULT skin but NOT with the Office2007 skin (using embedded skins)!!!!!
<link href="Skins723/Default/Editor.Default.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Default/Widgets.Default.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Default/Window.Default.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Default/toobar.Default.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Default/editorcontentarea.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Editor.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Widgets.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Window.css" rel="stylesheet" type="text/css" />
<link href="Skins723/Toolbar.css" rel="stylesheet" type="text/css" />
1 Answer, 1 is accepted
0
Hi Andy,
We will release later today Q2 SP1 of RadControls for ASP.NET AJAX. Please, upgrade your project to it once it becomes available and you should not experience problems with the external skins. If you still experience any problems after the upgrade, just open a support ticket and send a sample working project that demonstrates them. We will investigate them and try to provide a solution.
I also logged the Editor As TextBox problem in our bug tracking system. Indeed, Office2007 skin is one of the most used skins and we will do our best to fix the problem.
Kind regards,
Rumen
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
We will release later today Q2 SP1 of RadControls for ASP.NET AJAX. Please, upgrade your project to it once it becomes available and you should not experience problems with the external skins. If you still experience any problems after the upgrade, just open a support ticket and send a sample working project that demonstrates them. We will investigate them and try to provide a solution.
I also logged the Editor As TextBox problem in our bug tracking system. Indeed, Office2007 skin is one of the most used skins and we will do our best to fix the problem.
Kind regards,
Rumen
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.