Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support SwapChainPanel on W8.1 / WP8.1 and update templates to use SwapChainPanel #5521

Closed
wants to merge 2 commits into from

Conversation

nkast
Copy link
Contributor

@nkast nkast commented Feb 28, 2017

I found SwapChainBackgroundPanel behaving very unpredictable as I was testing #5520. That makes sense since it comes from W8.0, It wasn't supposed to run in window mode (W10).
(I found a workaround for #5520 out of nowhere , but that was after I had this PR ready! 8-) )

  • SwapChainBackgroundPanel & SwapChainPanel are wrapped into GenericSwapChainPanel.
  • SwapChainBackgroundPanel is still supported on W8.1 to allow easier upgrade from 3.5, the constructor is marked as [Obsolete].
  • W8.1 templates are updated to use SwapChainPanel.

@nkast nkast force-pushed the tnc_W81_SwapChainPanel branch 3 times, most recently from 1579e29 to 671a3f6 Compare March 3, 2017 01:14
@nkast nkast force-pushed the tnc_W81_SwapChainPanel branch 2 times, most recently from 1941943 to 1ac08ad Compare March 14, 2017 15:33
@nkast nkast force-pushed the tnc_W81_SwapChainPanel branch 2 times, most recently from cf15d27 to a9d37db Compare June 6, 2017 07:26
@nkast nkast force-pushed the tnc_W81_SwapChainPanel branch 2 times, most recently from 468bd21 to 3028a89 Compare July 11, 2017 13:56
@nkast nkast force-pushed the tnc_W81_SwapChainPanel branch 2 times, most recently from 691a9ea to 612add5 Compare September 1, 2017 02:30
@nkast nkast closed this Feb 21, 2018
@nkast nkast deleted the tnc_W81_SwapChainPanel branch February 21, 2018 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant