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

How to remove the flickering of WinUI3 windows on startup and shutdown #7892

Closed
2 tasks
MrJone2457 opened this issue Nov 8, 2022 · 2 comments
Closed
2 tasks
Labels
area-XamlWindow bug Something isn't working needs-triage Issue needs to be triaged by the area owners no-issue-activity team-Rendering Issue for the Rendering team

Comments

@MrJone2457
Copy link

Describe the bug

When I developed a WinUI3 screenshot application, I found a problem that I hadn't noticed before,
When the WinUI3 application starts and closes, if the system is the light theme, the flashing is white, and the visual effect is obvious. If the system is the black theme, the flashing is black. This problem may be related to this #5148 issue is somewhat related, but there seems to be no solution to this issue at present.

The application is launched in full screen mode, and the application interface displays a screenshot of the desktop.I personally want the effect to be as clean as the startup effect of the win11 Snipping Tool, or I can set the startup effect of fading in, and it is best to be clean and not flickering when it is closed. Is there any way?
Reference code https://github.com/MrJone2457/ScreenShot

Steps to reproduce the bug

Reference code
https://github.com/MrJone2457/ScreenShot

Expected behavior

No response

Screenshots

https://twitter.com/i/status/1589994651263852544
https://twitter.com/i/status/1590004799248171008
Don't know how to upload videos on github, check the video link on Twitter

NuGet package version

WinUI 3 - Windows App SDK 1.1.5

Windows app type

  • UWP
  • Win32

Device form factor

Desktop

Windows version

Windows 11 (22H2): Build 22621

Additional context

No response

@MrJone2457 MrJone2457 added the bug Something isn't working label Nov 8, 2022
@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Nov 8, 2022
@Scottj1s Scottj1s added team-Rendering Issue for the Rendering team area-XamlWindow and removed needs-triage Issue needs to be triaged by the area owners labels Dec 3, 2022
@github-actions
Copy link

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2023
@garrettpauls
Copy link

This is still an issue we're seeing as of WindowsAppSDK version 1.4.231219000, please consider reopening this.

It's difficult to create a small app that reproduces it reliably, but in our control-heavy business application it's pretty clear that the main Window is being shown before the content is loaded, which causes a bright white flicker before our darker UI loads (not theme dark, just darker than the default control theme).

It seems like a reasonable solution to this would be to not make the Window visible until the content has loaded and done a single render pass, but I don't know if that's an easy change to make internally. I'd be happy to use that as a workaround if there was a way to do that from an app implementation standpoint, but I haven't been able to find a way to trigger the controls to render before the Window becomes visible.

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-XamlWindow bug Something isn't working needs-triage Issue needs to be triaged by the area owners no-issue-activity team-Rendering Issue for the Rendering team
Projects
None yet
Development

No branches or pull requests

3 participants