[EDIT dec-15-2011] See last paragraph of this note for a solution.
I'm not getting this one to work with Q11/3/1115.
I have a dropdown combobox with a limited selection of skin names.
On selectedindex_changed I have
skinner is of type MySkinManager which is defined in another DLL inheriting from RadSkinManager.
The page markup then has this...
So a change to the ddSkins drowdown updates MySkinManager skinner, and I also update the entire page which is nested under pnlPage.
[EDITED dec-15-2011]
My default skin is WebBlue, identified in web.config. It looks like no matter which skin I try to change to, the page (pnlPage) seems like it loses its skinning. When this happens, the dropdown looks like it has it's fonts corrupted, changes to the selected index have no further affect on the screen, and the styles in the rest of the page aren't attractive. I can go back to WebBlue but I can't change to any other skin - it's as though none of the other skins have been pre-loaded. Do we need to specify the possible skins that we might be using at compile time so that they are available at runtime? If I set the default to Forest or any SkinX, I get the same behavior - anything other than SkinX shows up weird, and going back to the original SkinX looks great. Wherever possible I have set EnableViewState=true, EnableAjaxSkinRendering=true, EnableEmbeddedSkins=true, and EnableTheming=true. (That's just a shotgun approach to try to find what's wrong.) I've even added my RadFormDecorator as an AjaxUpdatedControl. But none of that seems to help.
Does anyone see what's wrong with the way that's written?
Also, I don't understand why we have to inherit from RadSkinManager rather than just invoking ChangeSkin on that object.
Thanks.
[EDIT dec-15-2011] I remembered that I already had code to do this in the form of a RadPageStylist server control. Looking back I found a reference to (Telerik's)
Vladimir Enchev's blog where he describes how to do this. Note, the code link on the blog page is bad but the
Live Demo works. I have the code for my purposes but it would be better if Telerik fixed that link. This is my solution, but it would be nice if Telerik made this a little more elegant.