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

BizHawkClient: Add error message if patching fails #2877

Merged
merged 2 commits into from
Apr 14, 2024

Conversation

Zunawe
Copy link
Collaborator

@Zunawe Zunawe commented Feb 29, 2024

What is this fixing or adding?

When a user opens a patch file and is asked to select their vanilla ROM through the settings api, if they close the file selection window or select a file that doesn't validate, the exception isn't visible to the user except through the console/log files. This adds a message to the client UI notifying the user what happened.

It's possible something like this should be closer to CommonClient or Settings, but would probably require quite a bit more UX design. At least compared to catching an error and logging something to the UI.

How was this tested?

Deleted my Emerald ROM and tried opening a patch file by providing

  1. No file
  2. An incorrect file
  3. A correct file

If this makes graphical changes, please attach screenshots.

Capture

@github-actions github-actions bot added the waiting-on: peer-review Issue/PR has not been reviewed by enough people yet. label Feb 29, 2024
worlds/_bizhawk/context.py Outdated Show resolved Hide resolved
@ScipioWright ScipioWright added the affects: core Issues/PRs that touch core and may need additional validation. label Feb 29, 2024
@github-actions github-actions bot removed the affects: core Issues/PRs that touch core and may need additional validation. label Mar 1, 2024
@alwaysintreble alwaysintreble added the is: enhancement Issues requesting new features or pull requests implementing new features. label Mar 28, 2024
Copy link
Collaborator

@beauxq beauxq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For other reviewers that might wonder:
_patch_and_run_game is currently only called inside a Utils.async_start
so I think it doesn't make any difference whether the exception is raised or not.

It seems a little strange that this function is async when it doesn't have any await in it, (and also calls its own async_start), but that's not related to the issue that this PR is addressing.

@Exempt-Medic Exempt-Medic added waiting-on: core-review Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer. and removed waiting-on: peer-review Issue/PR has not been reviewed by enough people yet. labels Apr 5, 2024
@Berserker66 Berserker66 merged commit 50fb70d into ArchipelagoMW:main Apr 14, 2024
15 checks passed
EmilyV99 pushed a commit to EmilyV99/Archipelago that referenced this pull request Apr 15, 2024
EmilyV99 pushed a commit to EmilyV99/Archipelago that referenced this pull request Apr 15, 2024
@Zunawe Zunawe deleted the bhc-patch-err-msg branch May 23, 2024 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is: enhancement Issues requesting new features or pull requests implementing new features. waiting-on: core-review Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants