Maximized Windows & Opener Issue

[Ross]

Hi,

I am experiencing an issue with maximized windows, and getting them to appear when more than window is visible.

There are three windows on the web page, each with an associated opener control (which sit in a seperate task bar).

When the windows are in a standard (non-maximized) state clicking on the opener control either shows the window, or if it is already open it brings it to the front so it can be seen.

When all the windows are open, and in a maxmized state, clicking on the opener control only brings the window title bar to the front, the contents of the window still remain hidden behind the other windows.

Is there a way to make sure that the entire window will appear on top?

Thanks.

[Georgi Tunev]

Hi Ross,

By design, a maximized RadWindow will have a higher zIndex than all other elements on the page. This however results in a behavior same as the one that you currently experience. There is a workaround that will allow you to set higher zIndex for every activated RadWindow that have been maximized. The idea is to use the OnClientShow and OnClientActivate eventhandlers of the control.
If you open a support ticket and send me a small sample project that shows your implementation, I will check it and rework it so it uses the approach that I mentioned above. We are also working on a KB article on the same subject and it will be available soon.

All the best,
Georgi Tunev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[-DJ-]

Hi Georgi,

I was some problems with the z-index of a maximized window as well.
I'm setting the z-index of the window manually, to make it overlap a radmenu.

However, when I maximized the window, the semi-transparent background that was overlaying the page, suddenly overlayed the window as well, making it impossible to interact with it.

The solution was to lower the z-index. So you have to be careful not to set the z-index of a window to high. While 9000 works well, something like 900000000 creates this problem.

The reason why the menu has a higher z-index by default than the window remains a mystery to me.

Regards,
-DJ-

[Tom]

I used Georgi's tip to keep the active RadWindow in the front by calling this client side OnClientActivate script:

function OnClientActivate(oWnd, args) {
    var windows = oManager.get_windows();
    var highestZ = 0;
    for (var i = 0; i < windows.length; i++) {
        var currZ = parseInt(windows[i].get_popupElement().style.zIndex);
        if (currZ > highestZ) highestZ = currZ;
    }
    //ensure that the activated RadWindow will always have
    //a higher z-Index than the other ones
    oWnd.get_popupElement().style.zIndex = highestZ + 1;
}

The important addition for my case is the parseInt usage. Without it, Firefox treats the currZ variable as a string and adding 1 to it makes the highest z-index value grows by a factor of 10 on each call.