Handling of size/resize with Toolkit on Windows RT XAML is inconsistent about sharpdx HOT 3 CLOSED

In the case of WinRT - the issue is caused by the fact that the Toolkit subscribes to SizeChagned event of the SwapChainBackgroundPanel before it is loaded. When the control is loaded and positioned during the layout pass - its size changes and the SizeChanged event is fired, leading to a backbuffer resize even when the game was not displayed yet.

For WinRT we can check if the control is loaded (by checking that either of ActualWidth or ActualHeight are not zero?) and if not - subscribe to the Loaded event and initialize the game in its handler, or load it immediately otherwise.

WP8 platform has also issues with what and when gets loaded - discussed here: http://www.sharpdx.org/forum/5-api-usage/3401-drawingsurfacebackgroundgrid-vs-drawingsurface-on-windows-phone-8-wp8#3953

On WP8 this behavior causes incorrect sizing of the game - as the control size is not known during the initialization - the image gets stretched (for example, the backbuffer size is 800x480, while the WP8 surface size is 480x800).

from sharpdx.

Back to requirements:

• We want to render to whatever is the resolution of the device: We should specify a PreferedBackBufferWidth/Height to 0 and let the system pick a valid resolution for the container surface.
• We want to specify a specific resolution, and let the rendering be stretched by the container surface. In case the container surface is resize, we should update the specific resolution according to the ratio of the resize

Currently this is not really the case: it is half of both with an invalid mix between fixed size and variable size.

Are these requirements fine? Any other ideas?

If we settle on some behavior before 2.5, I will try to look if It can be fixed for this version.

from sharpdx.

I am not sure about the second requirement - I suppose if developer has specified some fixed backbuffer size - it should not be changed. For example, it may be required to save backbuffer contents to a image - so the size should not be changed unexpectedly. Is it worth to have some flag that can enable or disable the automatic resizing behavior? (this is now implemented in SharpDXElement for WPF platform).
What do you think?

from sharpdx.