Timers Left Running After Window Closed

[Andy]

I have an 'editor.aspx' page that has some RadEditor controls and an asp:Timer control to perform auto-save.

The editor.aspx page is running inside a RadWindow but when the RadWindow is closed the timer continues running.

Why does this happen? Is there any way to stop the timers, as the Timer control is in 'editor.aspx' but the RadWindow is in the parent aspx page.

[Princy]

Hi Andy,

By default, RadWindow instances are cached to speed up response time after the first time they are shown and will not destroyed on clossing. You can prevent this caching by setting the DestroyOnClose property to True. Try setting the DestryOnClose property to true and see whether it stops the timers when clossing the RadWindow.

ASPX:

<telerik:radwindowmanager id="RadWindowManager1" DestroyOnClose="true" Modal="true" runat="server">
</telerik:radwindowmanager>

Thanks,
Princy.

[Georgi Tunev]

Hello Andy,

Indeed, Princy is right. I would just like to add some more info about the DestroyOnClose functionality. When this property is set to true, the window object will be destroyed once it is closed. This means that you will not be able to open that same RadWindow again until the page is reloaded. A new RadWindow with the default settings taken from the RadWindowManager will be opened instead. That is why in scenario like this, I suggest to set all needed properties (size, behavior, etc.) in the RadWindowManager OR as an alternative - to set them by using the client-side API when opening RadWindow.

Regards,
Georgi Tunev
the Telerik team

Check out Telerik Trainer , the state of the art learning tool for Telerik products.

[Andy]

This solution works perfectly for me. Thank you!