David Penny
Top achievements
Rank 2
Rank 2
David Penny
asked on 12 Mar 2010, 11:49 AM
Hi,
I have an app which uses the RadSkinManager throughout, and a weird issue where after carrying out operations in a RadWindow and closing it the skin is reverting to Default.
The app has a main page with a RadMenu across the top which opens all links in a RadWindow.
A RadGrid is shown in the opened RadWindow and to edit a record this in turn opens another RadWindow. If certain delete operations are carried out on the opened window, when the window is closed the skin on the RadGrid and page reverts to default. On closing this window the main calling window has also reverted to Default.
This can be fixed by refreshing the page, when the code to assign the skin is triggered.
Unfortunately the app is too large to provide as an example, and I'm not sure I could strip it down just to the action to reproduce, but I could provide a url and instructions on how to reproduce the issue if you need to look at it.
David Penny
I have an app which uses the RadSkinManager throughout, and a weird issue where after carrying out operations in a RadWindow and closing it the skin is reverting to Default.
The app has a main page with a RadMenu across the top which opens all links in a RadWindow.
A RadGrid is shown in the opened RadWindow and to edit a record this in turn opens another RadWindow. If certain delete operations are carried out on the opened window, when the window is closed the skin on the RadGrid and page reverts to default. On closing this window the main calling window has also reverted to Default.
This can be fixed by refreshing the page, when the code to assign the skin is triggered.
Unfortunately the app is too large to provide as an example, and I'm not sure I could strip it down just to the action to reproduce, but I could provide a url and instructions on how to reproduce the issue if you need to look at it.
David Penny
2 Answers, 1 is accepted
0
Hello David,
Unfortunately I'm unable to recreate the described behavior locally. I have created a small test app which tries to reproduce the scenario in question. Please take a look, maybe I'm missing something obvious.
Kind regards,
Rosen
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Unfortunately I'm unable to recreate the described behavior locally. I have created a small test app which tries to reproduce the scenario in question. Please take a look, maybe I'm missing something obvious.
Kind regards,
Rosen
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
David Penny
Top achievements
Rank 2
Rank 2
answered on 17 Mar 2010, 12:50 PM
Hi Rosen,
My apologies. I tracked this down to using RadCompression. When I set one of the options it was losing the Viewestate on my calling window and so the skin was reverting back to it's default value. Removed the Radcompression setting and it's now OK.
I thought I had posted an update, but must have forgotten.
David Penny
My apologies. I tracked this down to using RadCompression. When I set one of the options it was losing the Viewestate on my calling window and so the skin was reverting back to it's default value. Removed the Radcompression setting and it's now OK.
I thought I had posted an update, but must have forgotten.
David Penny