-
Notifications
You must be signed in to change notification settings - Fork 12
The Verification Update #2
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
Draft
SoyRA
wants to merge
3
commits into
sklauncher:master
Choose a base branch
from
SoyRA:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
DelTreefails to delete the old JRE folder, the script logs the error and then callsExit;, which terminates theRenameJREprocedure. This is a good step to prevent further operations on a potentially problematic directory state. However, this critical failure isn't directly communicated to the user. The main installation process might appear to complete successfully, but the JRE (a crucial component) would not be set up correctly, potentially leading to a non-functional application.Could we consider adding a user-facing error message before exiting the procedure? This would provide better feedback and help the user understand why the application might not work post-installation.
For example, you could use
MsgBox:Calling
Abort();after theMsgBoxwould terminate the entire setup process, which might be more appropriate if a failed JRE setup renders the application unusable. This would provide clearer feedback to the user about the installation status.