Stuart Hemming
Top achievements
Rank 2
Rank 2
Stuart Hemming
asked on 13 Apr 2012, 02:49 PM
When using RadWindows we always have KeepInScreenBounds = "True".
I work on a desktop machine with 2 monitors. If I set the browser to fullscreen mode, then open a RadWindow in my app and move it off to the far right of the screen, then take the browser out of fullscreen mode the RadWindow is completely off the screen and inaccessible.
I'm not sure if you can do anything about this, but it would be nice to ensure that, at least when KeepInScreenBounds=true, that the RadWindow moves when this happens.
--
Stuart
I work on a desktop machine with 2 monitors. If I set the browser to fullscreen mode, then open a RadWindow in my app and move it off to the far right of the screen, then take the browser out of fullscreen mode the RadWindow is completely off the screen and inaccessible.
I'm not sure if you can do anything about this, but it would be nice to ensure that, at least when KeepInScreenBounds=true, that the RadWindow moves when this happens.
--
Stuart
1 Answer, 1 is accepted
0
Hello Stuart,
The KeepInScreenBounds property is related to the user dragging the RadWindow and its initial showing. How it works, said shortly:
- when a RadWindow must be opened it is usually centered. If the size of the RadWindow is larger than the available viewport the titlebar will be (partially) hidden by default. KeepInScreenBounds checks for this and makes sure that the top left corner of the RadWIndow is in the top left corner of the browser viewport
- when the user releases the RadWindow after dragging or resizing the KeepInScreenBounds checks if part of it is outside of the visible viewport and again tries to return it to the closest position possible. For example, dragging a RadWindow downwards will make it stick to the bottom of the browser when the mouse is released. Also, the above logic is also applied - the top left corner of the RadWindow must be visible.
All that being said - what you are trying to achieve is not supported by the control. It does not autoamtically change its position according to a browser change in the same manner as pages with fixed layout do not change. It would be considered unexpected and therefore buggy behavior. The RadWindow would still be available on the page, only in its previous position - it is absolutely positioned and the page will spawn scrollbars as needed. Nevertheless, I will log this idea in our database and we will research its viability and implications. I cannot confirm neither when, nor if it will be implemented, but if it is - information about it will be available in the release notes.
Kind regards,
Marin
the Telerik team
The KeepInScreenBounds property is related to the user dragging the RadWindow and its initial showing. How it works, said shortly:
- when a RadWindow must be opened it is usually centered. If the size of the RadWindow is larger than the available viewport the titlebar will be (partially) hidden by default. KeepInScreenBounds checks for this and makes sure that the top left corner of the RadWIndow is in the top left corner of the browser viewport
- when the user releases the RadWindow after dragging or resizing the KeepInScreenBounds checks if part of it is outside of the visible viewport and again tries to return it to the closest position possible. For example, dragging a RadWindow downwards will make it stick to the bottom of the browser when the mouse is released. Also, the above logic is also applied - the top left corner of the RadWindow must be visible.
All that being said - what you are trying to achieve is not supported by the control. It does not autoamtically change its position according to a browser change in the same manner as pages with fixed layout do not change. It would be considered unexpected and therefore buggy behavior. The RadWindow would still be available on the page, only in its previous position - it is absolutely positioned and the page will spawn scrollbars as needed. Nevertheless, I will log this idea in our database and we will research its viability and implications. I cannot confirm neither when, nor if it will be implemented, but if it is - information about it will be available in the release notes.
Kind regards,
Marin
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.