The information for this control has to be the most confusing thing I've read in the Telerik documentation. One part says "Good practice is not to declare RadWindow in XAML as it is not logical to be part of the visual tree." then there's a bunch of examples doing just that. The attached project in the thread below, which the poster claims is to show using inheritance, does nothing of the sort but rather shows the RadWindow declared within the xaml of the parent control. Popup windows are often reused throughout the application (almost by definition, you might say), so this approach seems to be rather bad practice.
http://www.telerik.com/community/forums/silverlight/window/adding-contents-to-radwindow.aspx
Part of the problem for me might be that I'm coming from using the Microsoft ChildWindow, which is very simple and straightforward. They have a code template for it, and when you add it to the project you get a control that inherits from ChildWindow, as in really truly inherits.
Maybe the easiest thing is to just keep using that. What is the advantage of RadWindow over ChildWindow? What am I missing about how RadWindow is supposed to be used?
http://www.telerik.com/community/forums/silverlight/window/adding-contents-to-radwindow.aspx
Part of the problem for me might be that I'm coming from using the Microsoft ChildWindow, which is very simple and straightforward. They have a code template for it, and when you add it to the project you get a control that inherits from ChildWindow, as in really truly inherits.
Maybe the easiest thing is to just keep using that. What is the advantage of RadWindow over ChildWindow? What am I missing about how RadWindow is supposed to be used?