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

Bad user input behavior #41

Closed
unsaved opened this issue Jul 3, 2020 · 1 comment
Closed

Bad user input behavior #41

unsaved opened this issue Jul 3, 2020 · 1 comment

Comments

@unsaved
Copy link

unsaved commented Jul 3, 2020

User entered text often doesn't produce the results stated in the prompt. This is at least as bad with current version as from the version 1 week ago.

At 2 or 3 points during script execution the program just stops progressing and no prompt is given. Hitting the space bar nudges the script to continue.

At several points during script execution the prompt will not accept ENTER key until I enter some other key first. Sometimes hitting ENTER multiple times works, but I fear doing that because I don't know if it buffers up the multiple ENTERs to use the for subsequent prompts.

Sometimes prompts won't take any input at all until I refocus on the window (though I did nothing to take focus away from the script execution window).

Sometimes when I re-run it to see if disabled apps have reverted (which happened many times), if I see all of the apps are removed and nothing to do so just close the app-sel UI, the script freezes and there's nothing I can do but close the script window.

@farag2
Copy link
Owner

farag2 commented Jul 7, 2020

I can not reproduce. Tested on hundreds PCs. Never faced that.
https://github.com/farag2/Windows-10-Setup-Script#faq

@farag2 farag2 closed this as completed Jul 7, 2020
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

No branches or pull requests

2 participants