Re: WinRT changes for review

On Sun, Oct 2, 2016 at 3:04 PM, hardcoredaniel <[email protected]>
wrote:

> 1. I have not found anything useful to put into ddpi. I filled in the
> value for "ResolutionScale", but I do not know whether the raw DPI values
> need to be scaled anyway - so this was experimental only. I can also put in
> the mean of rawdpix and rawdpiy instead.
>

If those values give return values that are equal to the values returned by
the Win32 backend, I'd generally be fine with this.


>
> 2. I would be fine with a hint, one reason less to maintain an out-of-tree
> SDL :-) Last time we discussed it we did not conclude whether the hint is
> necessary, or triple-buffering should be enabled by default, because the
> additional memory consumption is not relevant nowadays.
>

I've started work on a patch (for a hypothetical,
SDL_HINT_RENDER_BUFFER_COUNT), and will try to post it to Bugzilla soon,
for review.


>
> 3. The implementation from the patch will only try to set the
> "PreferredLaunchWindowingMode" property if the switch to
> windowed/fullscreen worked. An implementation outside SDL would have to
> query the fullscreen state first (to check whether the call worked) and
> then set the property accordingly.
> However, if the property should be set independently of the result of the
> function call, it can be set externally.
> Too bad that "SetWindowFullscreen" cannot return success or failure...
>

Having internal SetWindowFullscreen functions be able to report errors
sounds interesting.  I'm wondering if there are downsides here, such as
quirky behavior on select platforms (I vaguely recall OSX-fullscreen'ing
being async, for example), that would prevent this operation from making
sense, in some cases.  :-/

-- David L.

_______________________________________________
SDL mailing list
[email protected]
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org