-
Notifications
You must be signed in to change notification settings - Fork 328
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
Proposal - CoreApp and app lifecycle helpers #9
Labels
Comments
Yes please! Using CoreApp is so much simpler. 👍 |
See also https://docs.microsoft.com/en-us/windows/win32/power/wm-powerbroadcast which provides more powers. |
Yes! I've always wanted to use |
Would love to see suspension support for all apps. |
Yes, I would like to have the option to apply lifecycle support to desktop apps (not just UWP). This would be great! |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Proposal: CoreApp Everywhere
Summary
Provide a variant of
CoreApplication
that gives Win32 apps the same common events as UWPs. Expose a set of common app/user/session lifecycle events for all kinds of apps to use under a single API surface.Rationale
While UWP has a rich app-lifecycle model for applications under system control, Win32 has historically made it hard to detect and react to app/user/system/session power and lifecycle events. There should be a single type that collects & generates events for the lifecycle of an app. As Windows' power management functionality improves having a single type collecting these events is critical.
Scope
Important Notes
The existing
CoreApplication
type mixes together basic app functionality like lifecycle and window generation. Reunion'sCoreApp
should expose only app lifecycle events. UWP activation paths likeOnActivated
should be moved to another object that's clearly about UWP activation and windowing behavior.The text was updated successfully, but these errors were encountered: