This repository has been archived by the owner on Aug 14, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 994
Login Screen #792
Labels
Comments
Thank you for creating an issue. We will normally respond within 24 hours. |
Closed
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
1 similar comment
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Not stale |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Not stale |
Closing as it's not possible |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
This is an awesome project and can actually be used in demoing software. We currently need to screen record login states for an app we are working on and have been looking for a simulation similar to what you have done to improve our recording which always blanks out the login form of Windows
Describe the solution you'd like
We would like to see a login and unlock screen added if you would be prepared to go this far. It would add some additional capabilities to your app that could make it quite a powerful simulated environment for demoing projects.
Describe alternatives you've considered
When we use current screen recording technologies, we have yet to find one that allows us to fully record the login and unlock screens of Windows. This makes trying to showcase an app that fires events whenever a user logs in or unlocks their desktop quite difficult to showcase visually without added explanation screens. Your demo could give us this capability which would reduce general screen recording complexities of Windows auth demos.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: