RadWindows implementation (3 layers of user controls)

2 posts, 0 answers
  1. Patrick
    Patrick avatar
    1 posts
    Member since:
    Apr 2011

    Posted 12 Sep 2011 Link to this post

    I have reviewed many topics about RadWindow, RadWindowManager etc, but I am having trouble understanding the approach that I should take.

    My goal is simple, I have a control heirarchy

    Page.aspx
    ==== RadTabStrip
    ========RadTab
    ============UserControl
    ============Modal content (UserControl)
    ============UserControl
    ======================= Modal Content (UserControl)

    See, I have nested controls that do their own thing, the need for modals / pop ups on different levels of the control tree, but each popup should appear as though it "owns the page".

    My question: How should I approach this generally? Should I use RadWindows on the Page.aspx and "Add" controls to them at run-time? Or is there a way to manage RadWindows on various levels? I just don't understand how to manage the windows in this scenario.

    Thanks,

    Patrick
  2. Marin Bratanov
    Admin
    Marin Bratanov avatar
    4614 posts

    Posted 13 Sep 2011 Link to this post

    Hello Patrick,

    I have already answered your support ticket on the matter and I am pasting my reply here as well for others who may have a similar question.

    I would like to ask that you do not post multiple threads for a single issue in the future, as this makes it harder to track the issue and conversation and also increases the response time.




    I assume that you are using RadTabStrip in combination with a RadMultiPage in a way similar to this online demo, just instead of images you put user controls in the RadPageViews. If this assumption is correct then the controls are part of the main page and there will be no issues in each user control having its own RadWindow with the static content you need (a simple example is attached and here is a video that shows the modal overlay covers the entire page in this scenario). You could, alternatively, put a RadWindowManager on the page that has all the RadWindows that you need for this page, but this defeats the purpose of user controls a bit.

    In case you are using PageViews with external content (i.e. iframes) it would be best if you declare the needed RadWindows in a RadWindowManager in the topmost frame (i.e. Page.aspx) so that they can cover the entire area. You could then call them by using window.top.radopen(null, windowName).

    On a side note - I advise that you upgrade to the latest version of our controls and to a newer version of .NET, since the one you are currently using does not support IE9 and the .NET 2.0 framework is no longer supported even by Microsoft.


    Regards,
    Marin
    the Telerik team

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